Actively exploited Security news
Intruder breached the Fugaku supercomputer through its status page and may have stolen users' SSH keys
Japan's RIKEN research institute disclosed on 16 November 2026 that an outside attacker spent 10 to 13 November inside the operations network of Fugaku, one of the world's most powerful supercomputers. The intruder got in through the public web page showing Fugaku's operating status, tampered with several servers and may have taken private SSH keys and access keys for other supercomputers and services from users' home directories. Some of the stolen credentials have already been tried elsewhere. Fugaku has been offline since 14 November.
Key points
- RIKEN confirmed unauthorised access to Fugaku's operational systems on 13 Nov 2026; its investigation puts the intruder inside from 10 to 13 November.
- The way in was the public Fugaku operating-status web page, where a software vulnerability was exploited. RIKEN has not yet named the flaw.
- Private SSH keys, access keys for external systems and research data files may have been taken from home directories, plus names, email addresses and user IDs.
- The attacker tried some of the credentials on other systems. Fugaku has been offline since 14 Nov and all user login keys have been invalidated.
What happened
RIKEN's Center for Computational Science in Kobe announced on 16 November 2026 that an outside attacker had broken into the operations network of the Fugaku supercomputer. Staff spotted suspicious traffic on 12 November and confirmed the intrusion at 16:33 Japan time on 13 November. The investigation so far places the attacker inside from 10 to 13 November.
The entry point was the publicly accessible web page showing Fugaku's operating status. From there the attacker moved into the internal operations network, tampered with several servers and installed unauthorised programs on some of them. RIKEN says a software vulnerability was exploited but has not disclosed which one or exactly how the break-in worked; the investigation continues. According to RIKEN, the operations system is run by an outside contractor.
What may have been exposed
- From the authentication system: names, email addresses and user IDs of Fugaku users (names and email addresses for the smaller Rikyu system). Up to 4,222 registered Fugaku users and 375 Rikyu users are affected.
- From home directories: some files were taken or may have been taken, including private SSH keys and access keys for supercomputers and services run by other organisations, as well as research data files.
- RIKEN says the attacker tried some of the stolen credentials on other systems. Whether that led to further break-ins is under investigation.
- As of 16 November, RIKEN had no concrete evidence that research results had leaked. It is still checking whether the files hold third parties' personal data.
What RIKEN has done
It isolated the affected systems (13 Nov), took Fugaku offline and blocked outside access (14 Nov), replaced administrative keys, stopped running and queued jobs and invalidated every user's login public key. It notified Japan's education and science ministry (MEXT), the HPCI network of computing centres and the Personal Information Protection Commission. No restart date has been announced.
What to do
- Fugaku and Rikyu users: revoke every SSH key, token and access key you kept on Fugaku at each service it unlocks, then issue new ones. Don't wait to learn whether your particular file was taken.
- Admins of HPC centres, cloud accounts and Git servers: find out which of your users work on Fugaku and review logins made with their keys since 10 November. Comparing key fingerprints in
authorized_keysagainst the keys users report as exposed is a quick start. - Watch for phishing: RIKEN warns about fake emails posing as Fugaku or RIKEN and says it never asks for passwords by email. Check suspicious links with our Link checker.
- A lesson for anyone running a status page: a public status page should have no path into your internal management network. Isolate it, patch it and monitor its outbound connections.
Shared research computing elsewhere has the same weak spot: unencrypted private keys to other systems sitting in home directories, rarely rotated. This is a good moment to audit that.
Timeline
Updates
- 17 Nov 2026: first version.
FAQ
Why does a Fugaku key leak matter to other organisations?
Researchers routinely keep private SSH keys and access keys on supercomputers so they can reach other computing centres, cloud storage or code repositories. Whoever holds such a key can log in as its owner. RIKEN says the attacker did try some of the stolen credentials on other systems; whether any attempt succeeded is still under investigation.
Was research data stolen?
RIKEN says files containing research data may have been taken from home directories, but as of 16 November 2026 it had no concrete evidence that research results had leaked. It is still checking whether the files contain third parties' personal data.
When will Fugaku be back?
RIKEN has not given a date. Before restarting, it plans to fix the exploited vulnerability, rebuild the compromised servers, rework the network configuration and add further security measures.
Sources
Spotted a mistake? Let us know and we will correct it openly.