Japan has taken its Fugaku supercomputer offline after intruders used a public dashboard to reach its internal operations network. Investigators also found attempts to access other systems using credentials obtained during the breach.
RIKEN, the research institute operating Fugaku in Kobe, suspended operations on Nov. 14. Information linked to up to 4,597 Fugaku and RIKYU users may have been exposed, including credentials stored for services outside RIKEN.
For Japanese researchers and APAC organizations sharing computing resources, the risk extends beyond interrupted jobs: a stolen key may remain valid on another network.
Intruders reached internal servers through a status dashboard
In its Nov. 17 disclosure, RIKEN said the intruder accessed Fugaku's operations network between Nov. 10 and 13 through a publicly accessible status page. Investigators have not determined the precise entry method.
The attacker tampered with several servers and installed unauthorized software. Files in user directories and authentication records were taken or may have been taken, including names, email addresses, user IDs, and stored SSH private keys.
RIKEN found no evidence that research results were exfiltrated. It confirmed attempts to use some stolen credentials against other systems, but whether those attempts caused additional damage remains under investigation.
Fugaku's outage disrupts research and raises cross-network risks
RIKEN stopped running and queued computing jobs, blocked external access, and invalidated Fugaku login keys. The institute plans to rebuild affected servers and revise network safeguards before restarting, with no restart date announced.
Fugaku supports scientific and industrial computing in Japan, including projects that depend on shared high-performance infrastructure. Japan's Chief Cabinet Secretary Minoru Kihara said the system "plays a vital role in our country's research and development infrastructure," according to The Japan Times.
Japan had separately announced a $63 million cybersecurity package focused on vulnerability testing and incident response before the Fugaku breach became public. The package was not announced as a response to this incident.
For APAC research partners, the immediate concern is whether an SSH key stored on Fugaku was also trusted by an institution's own servers. Such access could remain usable even after Fugaku is isolated. RIKEN has not confirmed whether the attempts to access outside systems succeeded.
How APAC organizations can protect against similar attacks
RIKEN urged affected users to revoke credentials stored on Fugaku and warned against phishing emails impersonating the institute. Response priorities differ depending on whether an organization used the system directly or is reviewing similar exposure risks.
Audience | Recommended security actions |
|---|---|
| Fugaku and RIKYU users in Japan | Revoke exposed SSH keys and tokens at external services, then issue replacements. Watch for impersonation emails and check official RIKEN updates on accounts and suspended jobs. |
| APAC universities and HPC operators | Restrict public management dashboards, separate monitoring services from internal networks, and audit cross-institution accounts and login activity. |
| Businesses and research partners | Identify projects dependent on Fugaku, assess delayed simulations, and confirm whether employees or contractors stored credentials used across multiple services. |
| Security and vendor teams | Review access controls, inspect authentication logs for suspicious attempts, and test incident containment and recovery procedures. |
Shutting down Fugaku helps contain the breach, but stolen SSH keys and access tokens may still provide access to external systems that recognize them.
Research institutions and businesses that use shared credentials should revoke affected keys across connected services, issue replacements, and review authentication logs for unusual login attempts.
Security teams should also investigate suspicious activity to determine whether attackers gained further access or compromised additional systems.
For organizations across APAC that depend on shared research infrastructure, reviewing external access permissions and coordinating with partner institutions can help prevent an incident at one facility from affecting other networks.
Also read: For more on why exposed credentials require prompt action, read about thousands of leaked AWS access keys that remained active in 2026.





