Skip to main content
All incident reports
Incident report

Japan's Fugaku supercomputer taken offline after attack via public dashboard

RIKEN took the Fugaku supercomputer offline on 14 November after an intruder used its public status dashboard to reach internal servers and plant malware. The research centre says credentials and user details were exposed, but it has not established who was responsible or how the access worked.

· First published

The short version

  • The breach. RIKEN says an unauthorised party used the public dashboard showing Fugaku's operational status between 10 and 13 November to get into multiple internal servers. The intruder planted malware aimed at user data.
  • What was exposed. Names, email addresses and user IDs for 4,222 Fugaku users, and names and email addresses for 375 users of the Rikyu supercomputer. SSH private keys and access keys stored on users' computers, plus research data files held there, were also affected.
  • Containment. RIKEN shut Fugaku down on 14 November, disabled users' login keys and asked users to revoke and replace stored credentials. The centre says operations will resume only once it is satisfied it is safe.
  • No attribution. RIKEN has not said who was behind the intrusion. It says its investigation did not determine further unauthorised access or theft of research results, although some exposed access keys were used in attempts to reach other systems.

Timeline

DateEvent
10-13 NovAn unauthorised party uses Fugaku's public status dashboard to reach multiple internal servers and plant malware targeting user data.
14 NovRIKEN takes the Fugaku supercomputer offline and disables users' login keys.
17 NovThe incident is reported publicly; RIKEN says it has no further details to share at that point.

How the intrusion worked

Fugaku's operational status was displayed on a public dashboard. According to RIKEN, an intruder used that dashboard between 10 and 13 November to gain access to several internal servers, then installed malware that targeted user data. The centre operates Fugaku, a supercomputer used for research including drug discovery and weather forecasting, alongside the smaller Rikyu system.

RIKEN says the exact method of intrusion is still being investigated. Separately, it lists fixing the exploited software vulnerability among its remediation tasks, without describing the flaw. It has not said whether the weakness sat in the dashboard software itself or elsewhere on the path from the dashboard to internal systems.

The malware was directed at data belonging to users. RIKEN says some of the access keys it found were then used in attempts to connect to additional systems, but that the investigation did not establish further unauthorised access or the theft of research results.

Who is affected

The centre has published counts for two groups. Details of 4,222 Fugaku users were compromised, comprising names, email addresses and user IDs. For 375 Rikyu users, names and email addresses were compromised.

Also affected are SSH private keys and access keys that users kept on their computers, and research data files stored there. RIKEN has asked users to revoke and replace any credentials held on the supercomputer and to be alert to suspicious emails that impersonate the organisation.

What happens next

Beyond the shutdown and the disabling of login keys, RIKEN says its remediation includes rebuilding compromised servers, reviewing network configuration and adding AI-driven security measures. It has promised updates as the investigation produces findings, and a spokesperson told BleepingComputer there was nothing further to share at the time.

The centre has not given a date for returning Fugaku to service, saying only that it will resume when it has confirmed it is safe to do so.

What is not known yet

  • Who carried out the intrusion, and whether the group is a state actor, a criminal operation or an individual.
  • Which software vulnerability was exploited, and how the public dashboard was used to reach internal servers.
  • Whether any of the research data files stored on users' computers were copied out of the network.
  • How many of the exposed access keys were used, and which additional systems were targeted with them.
  • When Fugaku will return to service.

What to do

If you use Fugaku or Rikyu

  1. Revoke and replace every SSH key and access key you stored on the supercomputers, and treat those credentials as compromised.
  2. Check any research data you kept on the systems and review copies held elsewhere for unexpected changes.
  3. Watch for emails claiming to come from RIKEN and verify any request through a separate channel.

If you run research computing or a public status page

  1. Establish what your public dashboards and status pages can reach on the internal network, and restrict that reach.
  2. Review network configuration so that a compromised front-end service cannot move freely to internal servers.
  3. Inventory credentials stored on shared systems so they can be rotated quickly if one host is compromised.

For everyone else

  1. Treat internet-facing dashboards and status pages as part of your attack surface, not as decoration, and check what they expose.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.