RIKEN has confirmed unauthorised access to the operations system of Fugaku, Japan’s flagship supercomputer, and said that personal data and stored credentials for users of Fugaku and of Rikyu, its AI-for-science machine, may have been taken. In a 16 November notice, the institute said an outside party used a publicly accessible Fugaku operating-status dashboard as a foothold between 10 and 13 November, that the access was confirmed on 13 November, and that Fugaku was shut down at 04:30 Japan time on 14 November (19:30 GMT on 13 November). RIKEN’s computing centre, R-CCS, issued a same-day pointer to that account. The exact method of the intrusion, RIKEN said, is still under investigation.
The institute put the number of people whose data was taken, or may have been taken, at up to 4,222 registered Fugaku users and up to 375 registered Rikyu users, or up to 4,597 in total. For Fugaku users, that information includes names, email addresses and IDs; for Rikyu users, names and email addresses. RIKEN also said some files in users’ home directories may have been removed, including credentials stored for non-RIKEN supercomputers and services, such as SSH private keys and access keys, and other files, including research data. It said that, so far, it has found no specific evidence that research results leaked, and that it is still checking whether those files contain third parties’ personal information.
What RIKEN says happened, and what it has done
Suspicious traffic was detected on 12 November, RIKEN said, after which it began an investigation with the external contractor that maintains the operations system. The unauthorised access was confirmed at 16:33 Japan time on 13 November (07:33 GMT). Fugaku was taken offline and cut off from outside access at 04:30 Japan time the next morning. The institute said the intruder had improperly operated several internal servers, that unauthorised programs had been installed and some systems altered, and that the attacker had tried to use some of the obtained credentials to connect to other systems. It is investigating, with other organisations, whether that led to further harm.
RIKEN reported the incident to Japan’s Personal Information Protection Commission at 17:55 Japan time on 16 November (08:55 GMT), to the Ministry of Education, Culture, Sports, Science and Technology (MEXT) at 20:59 Japan time on 13 November (11:59 GMT), and to bodies in the HPCI high-performance computing infrastructure at 10:51 Japan time on 15 November (01:51 GMT). It said it isolated the system used in the intrusion on the evening of 13 November, replaced management keys the following evening, revoked all users’ login public keys, and on 15 November stopped running and queued jobs at the same time as it emailed users. It asked those users to revoke, at the destination services, any credentials they had stored on Fugaku, and warned them about messages that might impersonate the institute.
Fugaku, the successor to the K computer, has been in shared use since March 2021. Rikyu is being built up by R-CCS under RIKEN’s TRIP programme as an AI-for-science platform. RIKEN said Fugaku will be restarted only after it has addressed the exploited software vulnerability, rebuilt compromised servers, reviewed the network design and put further security measures in place. It also said it will review how operational roles are divided so that it can respond more quickly in an emergency.
The notice is a first official account from a Japanese research institution, not a completed forensic report, and it sits alongside other recent Japanese disclosures of unauthorised access and leaked contact data. Nulab this week said unauthorised access to Cacoo exposed about 792 inquiry records. NTT Data has reported a subcontractor breach that exposed Japanese bond buyers’ details, a reminder that outsourced operations can sit on the same path as a laboratory system. TSN’s earlier RIKEN file is different in kind: Quantinuum’s RIKEN upgrade completed the H2 system with 56 qubits, a research partnership, not this incident.
Revoked keys cannot retrieve a copy that may already have left
RIKEN’s figures should be read as the institute has written them: maxima, for information that was taken or that may have been taken. The 4,222 and 375 counts are registered-user totals at risk, not a confirmed export log. The home-directory claim is similarly careful. Some stored credentials for systems outside RIKEN, including SSH private keys and access keys, are in scope, as is research data, but the institute says it has not confirmed that research results actually left. Those two statements can both be true at once. A file can be in a directory the intruder reached without RIKEN yet having evidence that the file was copied out.
The more immediate risk, on RIKEN’s own account, is the credentials. The institute says the intruder already tried some of them on other systems, and it has told users to revoke those keys and tokens at the far end. Revoking Fugaku login public keys, isolating a server and shutting the machine down can stop further use of that path. They cannot, by themselves, recall a private key or access key that has already been copied. Until RIKEN or the destination operators say whether those attempted logins succeeded, the secondary-harm question remains open.
The foothold description should be kept equally tight. RIKEN says a public status dashboard was used as a way into the operations network between 10 and 13 November, and that the precise intrusion method is still being investigated. That is not a completed explanation of how the dashboard was turned into access, and it should not be filled in. The documented event is an official first notice: Fugaku is down, user contact data and some stored keys may have been taken, research-result leakage has not been shown, and a restart waits on the repairs RIKEN has listed.
How we sourced this
The account above is drawn from RIKEN’s Japanese notice of 16 November, with a same-day R-CCS page pointing to that notice. Translations into English are by TSN. Times in the originals are Japan time; GMT equivalents are given in the article.
Sources
- RIKEN, “スーパーコンピュータ「富岳」および「理究(りきゅう)」への不正アクセスによる個人情報漏えいの可能性について”, 16 November 2026
- RIKEN Center for Computational Science, same title, 16 November 2026
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
- Quantinuum RIKEN Upgrade Completes H2 With 56 Qubits is TSN’s most recent RIKEN file, a research-partnership account rather than this breach, and the right next stop for the institute’s wider computing work.
- Nulab Says Cacoo Access Exposed About 792 Inquiry Records
- NTT Data Subcontractor Breach Exposes Japanese Bond Buyers’ Details
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X