RIKEN says intruders reached Fugaku’s internal operational network through its public status dashboard. They tampered with multiple servers, installed malicious programs and obtained credentials. RIKEN confirms that some obtained credentials were used to attempt connections to other systems. Whether those attempts caused further damage remains under investigation.

The response extends beyond restoring the Japanese supercomputer. Anyone who stored an SSH private key or other service credential on Fugaku should invalidate it at the external destination and replace it. Disabling a user’s Fugaku login does not revoke the same user’s access elsewhere.

What RIKEN has established

RIKEN’s Japanese notice was published November 16. Its English notice followed on November 17, alongside Bill Toulas’s BleepingComputer report.

The primary notice gives this sequence, in Japan’s local time:

  • November 10–13: intruders used the public dashboard as a foothold into the operational network. The exact entry method remains under investigation.
  • November 12: suspicious network traffic prompted an investigation with the outside maintenance provider.
  • November 13: RIKEN confirmed unauthorized access and isolated the system used for entry.
  • November 14: it suspended Fugaku operations, blocked external access and replaced administrative keys.
  • November 15: it halted running and queued jobs, notified users and invalidated users’ login public keys.

The potentially exposed authentication records cover up to 4,222 Fugaku users and up to 375 RIKYU users. They include names and email addresses, plus user IDs for Fugaku. These are maximum affected populations, not a verified count of stolen records or successful attacks on individual users.

Files in Fugaku users’ home directories were also taken or may have been taken. The exposed categories include SSH private keys, access keys for other systems and research files. RIKEN says it has no concrete evidence that research results were exfiltrated and is checking whether third-party personal information was included.

Evidence status: operator-confirmed intrusion, server tampering and attempted use of obtained credentials. The notice combines confirmed and possible data removal; it does not establish that every listed file was stolen or that another institution was successfully breached.

Revoke trust where the credential works

RIKEN’s user guidance is specific about SSH: revoke or remove the corresponding public key from every external service where it is authorized, then generate a new key pair. Revoke and replace other stored credentials through their issuing services.

For affected researchers and their infrastructure teams:

  • Inventory credentials stored on Fugaku. Include access to other clusters, repositories, storage and services, rather than considering only the supercomputer account.
  • Invalidate old credentials at each destination. Replacing a local private-key file alone leaves the old key trusted wherever its public key remains authorized.
  • Review destination access records. Investigate unexpected use of those identities and preserve relevant logs. RIKEN has observed connection attempts, but has not published a complete downstream impact assessment.
  • Verify unexpected messages independently. RIKEN warns about impersonation and says it will never request passwords or personal information by email.

For operators elsewhere, this incident supports limiting credentials left on shared compute systems and separating a public dashboard from management networks. Those are defensive implications of the reported path, not a claim that a particular network design has already been proven responsible.

Recovery is still being scoped

RIKEN plans to address the exploited software vulnerability, rebuild compromised servers and review network configuration before resuming Fugaku. It also plans to revise emergency responsibilities with its maintenance provider.

Caveat: The reviewed notices identify no CVE, affected software version, fixed release, attacker or completed recovery date. RIKEN’s ongoing investigation cannot yet settle the full data loss or downstream impact.