Japan’s RIKEN research institute confirmed on November 17, 2026, that an unauthorized party accessed the operational network of its Fugaku supercomputer. RIKEN suspended Fugaku operations on November 14 and blocked external access while investigators assess the intrusion and possible exposure of user information.
What RIKEN confirmed
RIKEN said attackers accessed the network between November 10 and 13 through a publicly accessible page displaying Fugaku’s operational status. The precise technical method remains under investigation. Multiple internal servers were altered, including the installation of malicious programs.
Information associated with as many as 4,597 Fugaku and RIKYU users may have been taken, including names, email addresses and user identifiers. Files stored in Fugaku user home directories, potentially including SSH private keys, access keys and research data, were also at risk.
RIKEN confirmed attempts to use some obtained credentials to connect to other systems. It has not established whether those attempts caused additional compromise. The institute says there is currently no concrete evidence that research results were exfiltrated.
Response and operational impact
After confirming unauthorized access on November 13, RIKEN isolated the affected access path, suspended Fugaku operations on November 14, replaced administrative keys and invalidated user login public keys. Running and queued computing jobs were halted, and affected users were notified. RIKEN says operations will resume after compromised servers are rebuilt and security measures are completed.
Defensive actions for affected users and administrators
Revoke exposed credentials
Users who stored SSH private keys or access tokens on Fugaku should revoke their authorization on external systems, generate replacement key pairs and rotate other stored secrets. Changing only the Fugaku login key does not invalidate credentials accepted by other services.
Review access logs and isolate vulnerable interfaces
Administrators of connected systems should examine authentication logs for unexpected use of affected credentials, restrict public-facing management dashboards, and separate monitoring interfaces from sensitive operational networks. Users should also be alert for phishing emails impersonating RIKEN.
What remains unknown
RIKEN has not identified the attacker, disclosed a specific exploited vulnerability, or confirmed theft of research results. The full scope of any secondary compromise remains under investigation. This article will be updated if RIKEN releases materially new findings.