Japan’s flagship Fugaku supercomputer has been offline since November 14 after an intruder broke into its operations network, tampered with internal servers and took, or may have taken, user files that include SSH private keys and access keys for systems outside RIKEN. The research institute says up to 4,597 users of Fugaku and its newer AI supercomputer, RIKYU, may be affected.
RIKEN, which runs Fugaku through its Center for Computational Science (R-CCS) in Kobe, disclosed the incident on November 16 in a Japanese notice and an English version. It also confirmed that the intruder has already tried to use some of the stolen credentials to connect to other systems.
Public status dashboard used as the way in
According to RIKEN, an outside party used a publicly accessible web page that displayed Fugaku’s operational status (a dashboard) as a foothold into the machine’s internal operations network between November 10 and 13, 2026. The exact method used to get in is still under investigation, although RIKEN’s remediation plan refers to fixing “the exploited software vulnerability.”
Once inside, the intruder tampered with multiple internal servers. RIKEN says some of the compromised servers were altered, including through the installation of malicious programs, and that it is still examining the details.
Maintenance and management of the affected operations system were outsourced to an external provider. RIKEN says suspicious network traffic was detected on November 12, and it began investigating with that provider right away. The timeline it published is:
- November 12: Suspicious traffic detected and investigation started with the outside maintenance provider.
- November 13, 4:33 PM JST: Unauthorized access confirmed. The system used for the intrusion was isolated at 10:07 PM.
- November 14, 4:30 AM JST: Fugaku operations suspended and outside access blocked. Administrative keys were replaced at 8:20 PM.
- November 15, 4:18 PM JST: All running and queued jobs stopped, every user’s login public key invalidated, and users notified by email.
What data was taken or may have been taken
RIKEN lists 2 groups of affected information:
- User authentication system data: names, email addresses and user IDs for up to 4,222 Fugaku users, and names and email addresses for up to 375 RIKYU users, for a total of up to 4,597 people.
- Files in users’ home directories: credentials that users had stored for connecting to supercomputers and services outside RIKEN, such as SSH private keys and access keys, plus research data files that users kept on the system.
RIKEN says that, so far, it has found no concrete evidence that research results were leaked. It is still checking whether any of the affected files contain personal information about third parties.
The bigger concern is the stored credentials. RIKEN confirmed the intruder “attempted to connect to other systems using some of the obtained credentials.” It is working with relevant agencies to determine whether those attempts caused any secondary damage. Researchers often keep keys for their home clusters, code repositories and cloud accounts on shared machines like Fugaku, so a single intrusion can open doors well beyond the original target.
Regulators, HPCI partners and police notified
RIKEN reported the incident to Japan’s Ministry of Education, Culture, Sports, Science and Technology (MEXT) on November 13, to partner organizations in the High Performance Computing Infrastructure (HPCI) network on November 15, and to the Personal Information Protection Commission on November 16.
On November 18, Kyodo News reported that RIKEN has also reported the damage to police. Citing investigative sources, Kyodo said Hyogo Prefectural Police and other police authorities are gathering information with possible violations of Japan’s Unauthorized Computer Access Law in view. RIKEN told Kyodo it will cooperate with the police investigation.
No group has claimed the attack, and RIKEN has not attributed it to anyone.
When Fugaku will come back
RIKEN says Fugaku will resume operations only after it has fixed the exploited software vulnerability, rebuilt the compromised servers, reviewed its network configuration and added AI-assisted security measures. It also plans to quickly rework the division of roles in its operations and maintenance setup so it can respond faster in emergencies. No restart date has been given.
Fugaku, the successor to the K computer, entered shared use in March 2021 and is used by academic and industry researchers for work such as drug discovery, weather forecasting and disease simulations. RIKYU is a newer R-CCS supercomputer built for AI-driven scientific research.
What Fugaku and RIKYU users should do
RIKEN is asking users to take the following steps:
- Revoke any SSH private keys and other credentials that were stored on Fugaku at each service where they are authorized, and issue new ones.
- Be wary of suspicious emails that claim to come from Fugaku or RIKEN. RIKEN says it will never ask for passwords or similar information by email.
Administrators at other HPCI centers, universities and cloud services that trust keys used by Fugaku researchers should also review login logs for activity tied to those keys since November 10. Our guide on how to rotate leaked API keys after a platform breach walks through the process, and our guide on how to check a suspicious email safely can help with follow-up phishing.
The Fugaku case is the latest in a string of incidents where stolen keys spread an attack from one platform to others, including the trojanized Claude Code extension that planted SSH backdoors and the Barracuda cloud breach tied to a stolen AI vendor key.
BreachNews will update this story as RIKEN releases more findings on the intrusion method, the malicious programs and any confirmed misuse of stolen credentials.












