Skip to content
Security & Trust

Japan's Fugaku breach began at a public status dashboard, RIKEN says

The SSH keys stored on the machine may matter more than the status page that let the intruder in

W
WebPulse Newsroom
AI-assisted · 4 min read
Share on X LinkedIn
Japan's Fugaku breach began at a public status dashboard, RIKEN says
In brief
  • RIKEN says an outside party used a public status dashboard as a foothold into Fugaku's internal network between November 10 and 13, 2026.
  • Stored SSH keys and access keys for outside systems were taken or may have been, and RIKEN says some were used in connection attempts, so the incident can reach other organisations.
  • Leaders should ask how fast their teams can revoke every credential held on a shared system, and what public pages sit near internal networks.

A public status page was the foothold

A status dashboard tells people that a system is running. People read it to learn whether a system is running. RIKEN, the Japanese research institute, says that kind of page was where an intruder got into Fugaku. Fugaku is one of the country's flagship supercomputers.

RIKEN's Center for Computational Science says an outside party was inside the operations network from November 10 to 13. The intruder used a public web page showing Fugaku's operating status as a foothold. RIKEN saw suspicious traffic on November 12 and confirmed the intrusion on November 13. It stopped Fugaku at 4:30 a.m. on November 14.

The method is not settled. RIKEN says it is still investigating how the intruder got in. Its recovery plan does list dealing with an exploited software flaw. The material gives no CVE ID, so the flaw cannot be named. BleepingComputer reports that RIKEN has not said who was behind the attack.

What the intruder reached

RIKEN says the intruder operated several internal servers. On some of them, the intruder changed the system and installed malicious programs.

RIKEN says up to 4,222 Fugaku users and up to 375 users of Rikyu may be affected. Rikyu is a second machine used for AI research. For Fugaku users, the data includes names, email addresses and user IDs. For Rikyu users, it includes names and email addresses.

Some files from users' home directories were also taken, or may have been. Those files include SSH private keys and access keys. Users had stored them to connect to supercomputers and services outside RIKEN. Research data files were included too.

RIKEN says it has found no concrete sign that research results leaked. It is still checking whether those files hold other people's personal information.

The keys may be the bigger problem

Here is the idea worth taking from this case. A shared computing system works like a hotel's key cabinet. Users leave keys to many other doors there for convenience. Once the cabinet is open, every one of those doors is in question.

RIKEN says the intruder used some of the obtained credentials to try to connect to other systems. It is working with relevant agencies to learn whether any secondary harm followed. It has asked users to disable the stored keys at each destination and issue new ones. That puts work on organisations that never ran Fugaku.

This is our interpretation, not a finding of RIKEN's. When credentials sit on a shared machine, one breach can become many incidents. The first victim cannot close them alone.

How the front page sits near the back office

A status page looks harmless because it holds no secrets. But it must show live conditions, so it often draws on internal systems. That is general knowledge, not something RIKEN has described here. RIKEN says only that the page was the foothold.

RIKEN's response shows what cleanup costs. On the night of November 13, it isolated the system used in the intrusion. On November 14, it replaced administrative keys. On November 15, it stopped all running and queued jobs. It also cancelled every user's login public key and told users to revoke their stored credentials.

RIKEN also says it outsources maintenance of the operations system. It plans to review how roles are divided so it can act faster in an emergency. A RIKEN spokesperson told BleepingComputer there were no further details to share.

Fugaku will restart only after RIKEN has made it safe. BleepingComputer describes Fugaku as a 537-petaflop machine used in drug discovery and severe-weather forecasting.

Questions to put to your team

Start with the front door. Which status, monitoring or reporting pages can anyone on the internet reach? What do they connect to behind the scenes?

Then ask about stored credentials. Where do staff and researchers keep SSH keys and access keys on shared systems? How long would it take to revoke every one of them? With up to 4,222 Fugaku users affected, the revocation job could be large.

Finally, ask about vendors. If a contractor maintains a system, who decides when something looks wrong? How quickly can they act? RIKEN itself says that split of roles needs review.

A page that tells the world everything is fine can still give an intruder a first foothold. The harder problem is what is stored behind it.

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: RIKEN (Center for Computational Science).