Cybersecurity

Hackers stole SSH keys from Japan’s Fugaku supercomputer. Here’s why researchers everywhere should check theirs

By Nino Ray Yeh · November 21, 2026 · 1:46 pm AEDT · 6 min read
Rows of black Fugaku supercomputer racks with blue end panels bearing the Fugaku and Fujitsu logos, behind a rope barrier in a white machine hall at RIKEN in Kobe

Japan’s Fugaku, once the world’s fastest supercomputer, has been offline for a week after hackers got into its internal network through a public status web page. RIKEN, the government-backed research institute that runs it, now says the intruders took SSH private keys that some users had stored on the machine to log in to other computers and cloud services. More than half of those keys had no passphrase.

Fugaku is a shared facility used by researchers in universities and industry, including overseas collaborators. That turns a breach at one Japanese centre into a credential problem for every system those keys could open. Here’s what RIKEN has confirmed, what is still unknown, and what the incident means for researchers and IT teams in Australia.

What happened

RIKEN’s first notice, published on 16 November, says that from 10 to 13 November an outside party “gained unauthorized access to Fugaku’s internal operational network by using a publicly accessible web page displaying Fugaku’s operational status (the dashboard).” RIKEN says the exact method used is still under investigation.

The timeline it gives, in Japan time (two hours behind Sydney during daylight saving), runs like this:

  • 12 November: suspicious network traffic is detected. RIKEN says maintenance and management of the affected system were outsourced to an external provider, and the two began investigating.
  • 13 November, 4:33pm: unauthorised access is confirmed. The system used for the intrusion is isolated that night.
  • 14 November, 4:30am: Fugaku is shut down and external access blocked. Administrative keys are replaced that evening.
  • 15 November, 4:18pm: all running and queued jobs are halted, users are emailed, and the public keys every user had registered for login are invalidated.

RIKEN also says the intruder tampered with several internal servers, “including through the installation of malicious programs”. It reported the incident to Japan’s Personal Information Protection Commission and its science ministry, and in its second notice says it has briefed police in Saitama and Hyogo prefectures.

What was taken: SSH keys, not just names

RIKEN’s second notice, published on 20 November, widens the picture. For Fugaku’s 4,222 registered users, RIKEN says it has found traces showing the intruder accessed names, email addresses and user IDs. It has also confirmed that information entered at registration was affected, including addresses, affiliations, phone numbers and a record of which type of identity document each person used. RIKEN says the documents themselves were not leaked. Names and email addresses of up to 375 users of RIKYU, RIKEN’s separate AI-for-science supercomputer, may also have been exposed.

The more serious finding is about keys. RIKEN says it has “confirmed evidence that authentication credentials (such as SSH private keys) used to connect to external systems (e.g., supercomputers or cloud services operated by other organizations) were collected and exfiltrated from the home directories of some users.” It counts 430 such keys:

  • 233 private keys with no passphrase
  • 197 private keys protected by a passphrase

A private key without a passphrase works like a door key left in the lock: whoever holds the file can use it straight away. A passphrase adds a second barrier, though a stolen key file can still be attacked offline, so RIKEN is treating both groups as compromised.

RIKEN says it has seen evidence of external connections made with some of the stolen credentials, but has “not identified any other instances of misuse.” It is contacting affected users one by one and asking them to cancel and reissue their keys everywhere they are used. Its earlier notice said there was no evidence that research data had been taken, and that it was still checking whether any files included other people’s personal information.

Why this matters beyond Japan

Fugaku is not an obscure machine. It led the Top500 list of the world’s most powerful supercomputers from 2020 to 2022, and The Register reports it ranked ninth in the latest edition. It has 7,630,848 processor cores, according to The Register, and BleepingComputer notes it has been used for drug discovery, severe-weather forecasting and modelling the airborne spread of viruses. Researchers who had booked time on it are now waiting, and RIKEN has not given a restart date.

The bigger lesson is how much damage one weak point can do. A status dashboard is the kind of public page few people think of as risky. But according to RIKEN, it gave the attacker a path into the operational network and then into users’ home directories. Those directories held the keys that researchers use to connect to other supercomputers and cloud services. Supercomputing users often work across several facilities, so a key stored on one system may also open another.

There is an Australian link. In 2023, Australia’s National Computational Infrastructure (NCI) at ANU signed a memorandum of understanding with RIKEN’s Center for Computational Science to port an ANU molecular-modelling code to both Fugaku and NCI’s Gadi supercomputer. To be clear, neither RIKEN nor NCI has said any Australian systems or users were affected, and we have seen no evidence that they were. But any Australian researcher who used Fugaku, or kept keys for Australian systems there, should check their email for a notice from RIKEN and act on it.

What researchers and IT teams should do

RIKEN’s advice to its users is direct: “For any SSH private key stored on Fugaku, please revoke or remove the corresponding public key from each external service where it is authorized, and generate a new key pair.” Practical steps include:

  1. If you had a Fugaku or RIKYU account, assume any key, token or password stored in your home directory is compromised. Remove the matching public keys from every server, cloud account and Git service where they were authorised, then create new ones.
  2. If you run systems used by researchers, such as university clusters or cloud tenancies, check your logs for logins from keys that may have been kept on Fugaku, and consider asking users to rotate keys.
  3. Don’t store private keys on shared systems unless you have to. Where you do, protect them with a passphrase, and prefer agent forwarding, short-lived certificates or hardware security keys where your facility supports them.
  4. Watch for phishing. RIKEN warns users to be wary of emails claiming to be from Fugaku or RIKEN, and says it “will never ask for information such as passwords via email.” Registration details such as phone numbers and affiliations make targeted scams more convincing.

What we still don’t know

RIKEN hasn’t said how the dashboard was exploited, beyond promising to fix “any vulnerabilities in the exploited software”. It hasn’t attributed the attack to anyone. It also hasn’t said which external systems were reached with stolen keys, or whether any were damaged. Fugaku will only restart after RIKEN separates public services from the administrative network and rebuilds the affected servers. It has also promised an investigative committee with external experts.

Our view: this is a familiar story at an unusual address. As with the Optimizely supply-chain attack and the Java4Shell flaw we covered this week, the weak spot wasn’t the headline system but something connected to it, in this case a public status page run with an outside contractor. The 233 keys without passphrases are the part every organisation should take personally. Credentials left lying around on shared machines turn one breach into many.

Featured image: the Fugaku supercomputer at the RIKEN Center for Computational Science in Kobe, Japan. Photo: Barsaka2 / Wikimedia Commons, CC0 1.0 (cropped and resized).

Keep exploring

Read next

More stories worth your time from The Tech Boom.

Explore all tech stories
Share this story

Topics

Share with