RIKEN's Center for Computational Science says an external party used the publicly accessible operating-status page of the Fugaku supercomputer to enter its internal operational network between 2026-11-10 and 2026-11-13, tampered with internal servers and took or may have taken users' home-directory files and authentication data, including stored SSH private keys and access keys, some of which were tried against other systems; up to 4,222 Fugaku and 375 Rikyu users are affected (RIKEN, 2026-11-16 and 2026-11-17). RIKEN names no actor and the intrusion method is under investigation.
Aliases: Fugaku supercomputer cyberattack
Coverage
1
first 2026-11-18 → last 2026-11-18
Latest activity
2026-11-18
RIKEN Fugaku: intruder entered via the public status dashboard, took users' SSH keys and tried them elsewhere
Peak priority
notable
1 notable
Targets
education
sectors: education, technology · regions: apac
Sources cited
2
2 hosts
Defender insights
What each entry about RIKEN Fugaku and Rikyu unauthorized access (November 2026) tells a defender to do, newest first.
2 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials. Private cryptographic keys and certificates are used for authentication, encryption/decryption, and digital signatures. Common key and certificate file extensions include: .key, .pgp, .gpg, .ppk, .p12, .pem, .pfx, .cer, .p7b, .asc.
RIKEN's Center for Computational Science says that between 2026-11-10 and 2026-11-13 an external third party entered Fugaku's internal operational network through the publicly accessible web page that displays the supercomputer's operating status, and that the exact method is still under investigation (RIKEN, 2026-11-17). The intruder tampered with multiple internal servers, some of them with malicious programs, and took or may have taken files in users' home directories and user-authentication data, including credentials users had stored for connecting to other systems, such as SSH private keys and access keys; up to 4,222 Fugaku users and 375 Rikyu users are affected (RIKEN, 2026-11-17). RIKEN has confirmed that the intruder tried some of the obtained credentials against other systems and is checking whether damage or secondary misuse followed (RIKEN, 2026-11-17).
RIKEN and the external provider that maintains the system began investigating suspicious network traffic on 2026-11-12, confirmed the access on 2026-11-13 and suspended Fugaku on 2026-11-14 (RIKEN, 2026-11-17). It replaced the administrative keys, invalidated the public keys all users use to log in and halted all running and queued jobs, and it names no actor; it says there is no evidence yet that research data was exfiltrated (RIKEN, 2026-11-17; BleepingComputer, 2026-11-17).
an external third party gained unauthorized access to Fugaku’s internal operational network by using a publicly accessible web page displaying Fugaku’s operational status (the dashboard).
The exact method that was used to gain unauthorized access is currently under investigation.
Furthermore, we have confirmed that the unauthorized party attempted to connect to other systems using some of the obtained credentials.
RIKEN
incident18 Nov 05:08Zsingle-source · victim disclosureOpen finding →