Fugaku intrusion reached the supercomputer’s internal operational network through a public operations dashboard between November 10 and 13, 2026, according to RIKEN. The institute confirmed unauthorized access and server tampering, while the precise entry method remains under investigation.
Files in user home directories and authentication records were taken or may have been taken, RIKEN says. Stored SSH private keys and access keys for external services are among the possible exposures. Users should revoke and replace credentials kept on Fugaku; Leaked Credential Monitoring can help assess accounts beyond the research system.
What Did the Fugaku Intrusion Reach?
RIKEN says it detected suspicious traffic on November 12 and confirmed unauthorized access on November 13. It suspended Fugaku operations and blocked external access early on November 14, then emailed users on November 15.
The affected information includes names, email addresses and user IDs in the authentication system, plus files in home directories. RIKEN gives conflicting user counts across its overview and detailed table. Taken together, those figures indicate roughly 4,600 potentially affected people across Fugaku and RIKYU. That figure is a potential exposure estimate, not a confirmed count of people whose data was taken.
RIKEN also confirmed tampering on several internal servers, including installation of malicious programs. It has not identified the exact dashboard entry mechanism or attributed the activity to a named actor.
Why Do External Credentials Change the Response?
RIKEN confirmed attempts to connect to other systems with some obtained credentials. Its statement does not say those attempts succeeded, and it is investigating possible secondary harm. This makes each external service where a Fugaku-stored key was authorized a separate review target.
As context, Brandefense Blackhole counted five dark-chat posts matching Fugaku from August 19 through November 17, 2026. This is a count of posts mentioning the term, not evidence that those posts describe this incident or verify credential misuse.
RIKEN says it currently has no evidence that research data or files were exfiltrated. It is still examining whether third-party personal data was included, so the absence of evidence is not a final determination about every file.
What Should Users and Security Teams Do Now?
RIKEN has isolated the access path, replaced administrative keys and invalidated user login public keys. It asks users to invalidate credentials stored on Fugaku and warns that it will never request passwords or personal information by email.
- Identify stored credentialsList SSH private keys, access keys and other secrets previously kept on Fugaku.
- Revoke external accessRemove matching public keys from external services and revoke affected access keys.
- Issue replacementsGenerate new key pairs and credentials, then update authorized users and workloads.
- Review external activityCheck each connected service for attempts or unexpected activity from November 10 onward.
- Watch user messagesTreat emails claiming to seek Fugaku or RIKEN passwords as suspicious.
The steps above follow RIKEN’s revocation advice and extend the review to connected services. Use an incident response plan template to assign owners and preserve evidence for any suspicious access.
Review whether another team stored service credentials on the affected system before closing the case. The credential compromise glossary explains why possession of a secret and confirmed misuse require separate conclusions.
Frequently Asked Questions
Were Fugaku research files stolen?
RIKEN says it currently has no evidence that research data or files were exfiltrated. Its investigation remains open.
Did attackers access other systems?
RIKEN confirmed attempts to connect to other systems using some obtained credentials. It has not said those attempts succeeded.
How many users could be affected?
RIKEN’s overview and detailed table give inconsistent Fugaku counts. They indicate roughly 4,600 potentially affected people across Fugaku and RIKYU, but no precise total can be reconciled.
