Fugaku supercomputer breach via status dashboard: revoke stored SSH keys
RIKEN took the Fugaku supercomputer offline after an intrusion via its public dashboard; users should revoke SSH keys stored on it.
- Published
- Updated
- Exploitation
- Yes, RIKEN confirmed unauthorized access to internal servers and malware planted on some of them, as reported by BleepingComputer and GBHackers
What happened
BleepingComputer reports that RIKEN’s Center for Computational Science took Fugaku offline after a security breach. Between November 10 and 13, an unauthorized party exploited the public dashboard that shows Fugaku’s operational status and gained access to multiple internal servers (BleepingComputer). GBHackers, citing a RIKEN incident notice dated November 16, gives the same dates and the same starting point (GBHackers).
BleepingComputer says RIKEN has yet to determine the access method. GBHackers says RIKEN has not disclosed how the intruder moved from the dashboard into the internal network. BleepingComputer says investigators confirmed the intruder planted malware on some servers that targeted user data. GBHackers says malicious programs were installed on some servers. BleepingComputer also says RIKEN’s remediation includes fixing the exploited software vulnerability. No CVE identifier is given in the sources, so the specific flaw is not confirmed.
Data reported as compromised:
- Names, email addresses and user IDs of 4,222 Fugaku users (BleepingComputer). GBHackers says up to 4,222.
- Names and email addresses of 375 Rikyu users (BleepingComputer). GBHackers says up to 375.
- SSH private keys and access keys. BleepingComputer says they were stored on users’ computers. GBHackers describes files in Fugaku users’ home directories, some containing credentials for external computing systems and services.
- Research data files, per BleepingComputer. GBHackers says RIKEN has found no concrete evidence that research data was taken and is still checking whether affected files contained third-party personal information.
DataBreaches.net’s headline and GBHackers both put the number of users at risk at up to 4,597 (DataBreaches.net). GBHackers describes this as an upper bound for potentially affected users, not a confirmed count of stolen credentials. It also says RIKEN identified Fugaku’s operational network as the compromised environment and did not report a separate intrusion into Rikyu.
BleepingComputer says the intruder used some of the access keys in attempts to connect to additional systems, but the investigation did not determine further unauthorized access or theft of research results. GBHackers says RIKEN confirmed the connection attempts and that investigators have not established whether they caused further damage.
Timeline details differ slightly between outlets. BleepingComputer says RIKEN shut down Fugaku on November 14 and disabled users’ login keys. GBHackers says RIKEN detected suspicious traffic on November 12, confirmed unauthorized access at 4:33 p.m. on November 13, and suspended Fugaku operations at 4:30 a.m. the next morning. It adds that on November 15 RIKEN emailed users, halted all running and queued jobs, and invalidated Fugaku login keys.
The attack has not been attributed. RIKEN has given no restart date, and says Fugaku will resume only once it is safe. Planned steps include fixing the exploited weakness, rebuilding compromised servers, and reviewing the network configuration. Both outlets also mention AI-driven or AI-assisted security measures. A RIKEN spokesperson told BleepingComputer there were no further details to share and that updates would follow as the investigation progresses.
Am I affected?
You may be affected if you are a Fugaku or Rikyu user. The reported exposure covers account details for up to 4,222 Fugaku users and up to 375 Rikyu users, plus SSH private keys, access keys and other files kept by users, including credentials in home directories on Fugaku.
RIKEN’s investigation is still under way, and the sources do not confirm the full extent of what was taken. Whether a specific account or file was among those affected is not confirmed. Contact RIKEN directly if you are unsure about your own account.
What to do now
- Remove the public keys matching any SSH private key you stored on Fugaku from every external service that authorizes them, then generate new key pairs. This is RIKEN’s guidance as reported by GBHackers.
- Revoke and replace any other credentials or access keys stored on Fugaku, using the services that issued them. GBHackers notes that disabling Fugaku logins does not revoke credentials trusted elsewhere.
- Be cautious with emails that appear to come from RIKEN or Fugaku. GBHackers reports RIKEN says it would never ask for passwords or other personal information by email.
- Follow RIKEN’s official notices for restart timing and new findings. The sources give no restart date.