RIKEN announced on November 16, 2026, that an outside party gained unauthorized access to the operations system of the Fugaku supercomputer run by its Center for Computational Science (R-CCS). User names and email addresses, along with SSH private keys, other credentials, and research data stored in users' home directories, were taken or may have been taken, according to the institute. Fugaku has been shut down since early on November 14, and no date for restarting it had been given at the time of writing.

Up to 4,597 Users of Fugaku and Rikyu Are Affected

According to RIKEN, information registered in the user authentication system was leaked or may have been leaked for up to 4,597 people. That breaks down into up to 4,222 Fugaku users and up to 375 users of Rikyu, a supercomputer that R-CCS is building for AI for Science development.

Affected groupUsers (maximum)Data involved
Fugaku users4,222Name, email address, ID
Rikyu users375Name, email address

Separately, some files stored in Fugaku users' home directories were also affected. They include credentials such as SSH private keys and access keys used to connect to supercomputers and services outside RIKEN, as well as research data that users had saved. RIKEN says it has not so far confirmed any specific evidence that research results were leaked. It is also still checking whether the affected files contain personal information about third parties.

A Public Dashboard Served as the Entry Point

The unauthorized access took place from November 10 to 13, according to the announcement. The intruder used a web page published on the internet that showed Fugaku's operating status (a dashboard) as a foothold to get into the internal network of the operations system. RIKEN has not disclosed the specific method of intrusion, which remains under investigation.

The intruder manipulated several internal servers without authorization, and tampering, such as the installation of unauthorized programs, was confirmed on some of them. The intruder also used some of the stolen credentials to try to connect to other systems. RIKEN says it is investigating with relevant organizations whether there has been any secondary damage.

From Detection to Shutdown and a Halt of All Jobs

Maintenance of Fugaku's operations system is outsourced, and after suspicious traffic was detected on November 12, RIKEN began investigating together with the contractor. It confirmed the unauthorized access at 4:33 p.m. JST on November 13 and isolated the system used in the intrusion at 10:07 p.m. JST the same day.

At 4:30 a.m. JST on November 14, RIKEN stopped Fugaku and cut off external access. It replaced its administrative keys at 8:20 p.m. JST that day. At 4:18 p.m. JST on November 15, it stopped all running and queued computing jobs, disabled every user's login public key, and notified users of the incident by email.

RIKEN says it reported the incident to Japan's Ministry of Education, Culture, Sports, Science and Technology on November 13, to HPCI-related organizations on November 15, and to Japan's Personal Information Protection Commission on November 16.

Users Must Revoke Keys at the Services They Connect To

RIKEN is asking users to revoke the SSH private keys and other credentials they stored on Fugaku at each connected service, and to reissue any keys or credentials they need. It is also warning users about suspicious emails pretending to come from Fugaku or RIKEN, and says it never asks for passwords or similar information by email.

Operations will resume only after measures to prevent a recurrence are in place. RIKEN listed fixing the exploited software vulnerability, rebuilding the compromised servers, reviewing the network configuration, and deploying AI-based security measures. It also plans to promptly revise the division of roles in its operations and maintenance setup so it can respond faster in emergencies.

Our Take

RIKEN published its timeline down to the minute and asked users to revoke keys at the services they connect to, which is a sound response for limiting a chain of damage. Disabling login public keys on Fugaku alone cannot protect outside systems that accept the private keys that may have been taken. Since the intruder actually tried to connect to other systems, the impact could extend beyond Fugaku.

That said, the fact that a publicly accessible status page became a gateway into the internal network suggests there were problems separating public-facing systems from operational ones. Details of the exploited vulnerability had not been disclosed at the time of writing. Even so, the planned measures include a review of the network configuration, and a fuller explanation of the cause will likely be a precondition for restarting operations.

Summary

The Fugaku supercomputer was breached via a public dashboard, and data on up to 4,597 users, along with credentials for outside connections and research data, may have been taken. Fugaku and Rikyu users need to revoke and reissue, at each connected service, the keys and credentials they kept on Fugaku. Fugaku remains offline, and RIKEN says it will restart operations after putting measures in place to prevent a recurrence.