4,222 registered users of Fugaku are at risk, RIKEN says — and the organisation does not yet know how far the breach reached.
RIKEN's account of the intrusion
The RIKEN Center for Computational Science disclosed that between November 10 and 13 an unknown actor attacked a web dashboard that displays operational-status data for the Fugaku supercomputer. RIKEN said the attack appeared to allow lateral movement across its internal network; attackers reached servers that store data belonging to authorised users and installed malware there. RIKEN issued the statement "yesterday" and has promised a detailed investigation into the incident.
Data exposed: users' names, emails and credentials
RIKEN reports the affected servers stored users' names and email addresses, plus credentials used to access supercomputers and services not operated by RIKEN. The attacker has tried to use those credentials, and RIKEN is working with the organisations that host those other supercomputers to investigate whether the attempts succeeded. At present RIKEN says it cannot state with certainty what information attackers were able to access or steal beyond the populations it has identified as at risk.

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleScope: who and what are at risk
RIKEN has identified 4,222 registered users of Fugaku as at risk and 375 registered users of Rikyu. On November 13, RIKEN says, someone attempted to log onto Fugaku; the organisation quickly took the machine offline. RIKEN has found no evidence so far that users' research data has leaked, but it is not yet sure what information left the building or whether any of the material contains data describing third parties.
Fugaku and Rikyu: compute scale and the consequences of misuse
Fugaku comprises 158,976 nodes, each packing a 48-core processor and 32 GiB of available RAM — a total of 7,630,848 cores and over five petabytes of memory, RIKEN said. Those specifications helped Fugaku top the Top500 supercomputer lists from 2020 through 2022; on the update released on Tuesday it ranks ninth. RIKEN's other supercomputer, Rikyu, operates 288,000 cores.
RIKEN warned that if attackers managed to run a workload on either machine, they could "do a lot of damage." The intrusion has already had immediate operational consequences: Fugaku is currently offline, and because RIKEN schedules use of the machine the outage will disrupt researchers who were waiting for their turn to run jobs.
What this means for host organisations, researchers, and policymakers
- Host organisations and other supercomputer operators: RIKEN is coordinating with the organisations that host other affected services to determine whether the exposed credentials were abused to gain access elsewhere. Those organisations will need to validate account activity and assess whether malicious workloads or data exfiltration occurred.
- Researchers and scheduled users of Fugaku and Rikyu: users face delays while Fugaku remains offline. Although RIKEN has found no evidence of leaked research data so far, affected users should expect communications and potential requirements to verify account security and investigate whether any credentials in the now-exposed stores were reused across services.
- Policymakers and government cyber-response planners: RIKEN characterised the breach as the latest in a string of significant cyberattacks that have struck Japanese clouds, telcos, retailers and government agencies. That wave prompted Tokyo to release emergency funds aimed at shoring up the nation's cyber-defences — a context RIKEN cited as part of the broader incident landscape.
RIKEN's immediate actions are to continue the investigation, coordinate with other compute service operators, and keep Fugaku offline while assessing the breach. The organisation does not yet know how the initial compromise occurred, what exact data left its systems, or whether attackers succeeded in penetrating other hosts with the stolen credentials.
The concrete next steps the record leaves in focus are procedural and binary: complete the promised, detailed investigation; determine whether the credential use attempts succeeded; and restore Fugaku to service once RIKEN is satisfied systems and schedules are secure. Until those answers arrive, thousands of users remain in limbo and a high-capacity national research asset stays offline.




