The case is not a Windows story. It is a good reminder for anyone who runs shared infrastructure that a "harmless" public page can be the front door, and that stored credentials turn one breach into several.
What happened, and when
RIKEN's Center for Computational Science (R-CCS) says the intrusion ran from November 10 to 13, 2026. According to the institute's notice, the attacker used a publicly accessible webpage showing Fugaku's operating status as the foothold into the internal operational network. RIKEN has not yet determined the exact technique.
The timeline in RIKEN's notice:
- November 12: Suspicious network traffic is detected. Maintenance of the affected system was outsourced to an external provider, and RIKEN began investigating with that provider.
- November 13, 4:33 p.m.: Unauthorized access is confirmed. The compromised system is isolated at 10:07 p.m.
- November 14, 4:30 a.m.: Fugaku operations are suspended and external access is blocked. Administrative keys are replaced at 8:20 p.m.
- November 15, 4:18 p.m.: All running and queued jobs are halted, users' login public keys are invalidated, and users are emailed.
- November 17: RIKEN publishes its public notice.
One detail matters for the "how bad was it" question. RIKEN says it reported the incident to Japan's education and science ministry (MEXT) on November 13, to the Personal Information Protection Commission on November 16, and to the HPCI organizations on November 15.
Japanese press coverage adds a few details. Jiji Press reports that the outsourcing company in charge of maintaining Fugaku's operation system detected the suspicious communication. The Japan Times reports that the status webpage has since been made unavailable. It also quotes Chief Cabinet Secretary Minoru Kihara saying Fugaku is vital research infrastructure and that security should be a priority while limiting the impact on research.
What may have been exposed
RIKEN says files in users' home directories and information in the user authentication system were taken or may have been taken. The potentially affected data falls into two groups.
User authentication records:
- Names, email addresses and user IDs of Fugaku users.
- Names and email addresses of users of RIKYU, RIKEN's AI-for-Science supercomputer.
Home directory contents:
- Credentials users had stored for connecting to systems outside RIKEN, including SSH private keys and access keys.
- Files users had stored, including research data.
RIKEN also says some compromised servers were tampered with, including by installing malicious programs. It has confirmed that the attacker tried to use some of the stolen credentials to connect to other systems. It is working with relevant agencies to find out whether any damage or secondary harm resulted.
A note on the numbers
The headcount is slightly muddled. RIKEN's overview says up to 4,222 Fugaku users and up to 375 RIKYU users may be affected. The itemized list in the same notice gives up to 4,224 Fugaku users, with a combined total of up to 4,597 people. 4,222 plus 375 equals 4,597, so the 4,222 figure is the one consistent with the total. The 4,224 looks like a typo, though RIKEN hasn't said so. Either way, these are ceilings for who might be affected. They are not a confirmed count of whose data was stolen.
What is confirmed and what is not
Some of the early headlines blur these lines, so it's worth separating them.
- Confirmed: An outside party gained unauthorized access and tampered with multiple internal servers. Malicious programs were installed on some of them. Credentials were used in connection attempts against other systems.
- Taken or possibly taken: Home-directory files and authentication records. RIKEN's wording is deliberately hedged.
- Not established: RIKEN says there is no concrete evidence that research data left the system. It is still checking whether third parties' personal information was in the affected files. That is different from proof that nothing was copied.
- Not established: Whether the connection attempts using stolen credentials succeeded anywhere. RIKEN says it is investigating.
- Unknown: The attacker's identity, and the exact intrusion method. RIKEN has attributed the attack to no one.
Why the dashboard detail matters
Status pages feel low-risk. They show uptime, queue depth and maybe node counts. But they usually sit on a host that can see the internal network, because that is where the data comes from. If the page or its underlying software has a flaw, the attacker lands somewhere useful.
RIKEN's own remediation list hints at this. It says it will address vulnerabilities in the exploited software, rebuild the compromised servers and review network configuration. So the notice does point to a software vulnerability, although the entry method is officially still under investigation. RIKEN also plans to review how responsibilities for operations and maintenance are divided, so it can respond to emergencies faster. That reads as an acknowledgment that outsourced maintenance and in-house ownership need clearer lines. This is my interpretation of the notice, not a RIKEN finding.
The notice also says RIKEN will implement "state-of-the-art security measures utilizing AI." It gives no detail. Treat that as an intention, not a control you can evaluate. The unglamorous items on the list, patching, rebuilding and network segmentation, are the ones likely to do the work.
The part sysadmins should steal: stored credentials
The most consequential finding may be where the loot was: home directories. Researchers on shared clusters often keep SSH keys and access tokens there for convenience. They use them to push to repositories, reach other HPC centers, or move data to cloud storage. When the cluster falls, those keys fall too. As one Japanese security site put it, the keys opened doors to other supercomputers and services outside RIKEN.
RIKEN has invalidated the public keys users employ to log in to Fugaku. That only protects Fugaku. It does nothing about keys and tokens stored on Fugaku that grant access elsewhere.
What RIKEN asks users to do
- For any SSH private key stored on Fugaku, revoke or remove the matching public key at each external service where it is authorized.
- Generate a new key pair.
- Revoke and replace any other authentication credentials stored on Fugaku, using the relevant service.
- Be wary of email claiming to come from Fugaku or RIKEN. RIKEN says it will never ask for a password or personal information by email.
Because the exposure is of names and email addresses, phishing is the obvious follow-on risk. Expect lures that mention the outage, key resets or account verification.
Broader checklist for admins of shared systems
These steps are general good practice, not RIKEN guidance:
- Inventory which credentials live in user home directories on shared hosts, and treat all of them as exposed after a compromise.
- Revoke keys at the destination, not just at the source system.
- Review logs at downstream services for logins using the affected keys, around and after the incident window.
- Where possible, move to short-lived credentials or hardware-backed keys instead of long-lived private keys on disk.
- Put anything that touches the internal network, including status pages, behind the same patching and monitoring regime as production systems.
Impact on researchers and what's next
Fugaku was ranked the world's fastest supercomputer from June 2020 until Frontier overtook it in May 2022. Japan Times coverage describes it as developed with Fujitsu at a cost of ¥130 billion. It is used for drug discovery, severe-weather forecasting and simulations of airborne virus transmission, and RIKYU began operations last month for AI-driven scientific research.
RIKEN says Fugaku will return to service only after the preventive measures are done. The notice gives no restart date. It promises prompt disclosure of new findings, and for now it is the best primary source on the incident.
Bottom line
This is a classic chain: a public-facing status page, an internal network behind it, and stored credentials in user directories. The scale is large, with up to 4,597 people potentially affected. The confirmed damage is still bounded by what RIKEN has actually verified. If you run shared compute or any multi-user system, the lesson is plain. Audit what your users keep in their home directories, and rotate those secrets at the destination before someone else uses them.
References
- Japan takes Fugaku supercomputer offlline after cyberattack BleepingComputer · 2026-11-17T15:51:21-05:00
- Notice regarding a possible personal information leak affecting Fugaku and RIKYU users following unauthorized access to the supercomputer Fugaku | RIKEN riken.jp
- Japan’s most powerful supercomputer hit by unauthorized access - The Japan Times japantimes.co.jp