Skip to content
TrustList
News

RIKEN halts Fugaku after intrusion; 4,222 users told keys are at risk

Editorial

By TrustList Editorial

The notice also covers up to 375 users of the RIKYU system, and says credentials people stored to reach services outside RIKEN were among the data exposed.

About RIKEN halts Fugaku after intrusion; 4,222 users told keys are at risk

RIKEN halts Fugaku after intrusion; 4,222 users told keys are at risk

17 November 2026: RIKEN has suspended Japan's Fugaku supercomputer after an outside party broke into a system used to operate it, and says files in users' home directories and data in the user authentication system were taken or may have been. Up to 4,222 Fugaku users and up to 375 users of its RIKYU system may be affected, and the exposed data includes credentials people had stored for connecting to services outside RIKEN.

Not yet independently verified. Everything here is from RIKEN's own notice. It gives no cause, no description of the attacker and no restart date, and it does not name the system that was first accessed. The Japan Times has also reported the incident. We will update this when it can be confirmed, and remove this note.

Two days from intrusion to shutdown

The notice from RIKEN gives a short timeline:

  • 12 November: a system involved in operating Fugaku, at the RIKEN Center for Computational Science in Kobe, is accessed without authorisation by an external third party;
  • 13 November: RIKEN confirms the access;
  • 14 November, 4:30 a.m.: Fugaku operations are suspended and access from outside is blocked.

RIKEN says the scope and the cause are under investigation and that measures to prevent a recurrence are being put in place. It gives no date for the machine to return to service.

Names, email addresses and stored credentials

Three kinds of information are named: users' names, their email addresses, and authentication credentials that users kept on the system in order to connect to systems or services outside RIKEN. The last is the part that travels. A researcher who logs in to Fugaku and from there pushes code to a repository, pulls data from a cloud bucket or reaches a university cluster usually leaves a key or token in the home directory to do it.

The notice draws no line between kinds of user, so a company with staff accounts on either system has the same exposure as a university group.

Which keys to replace first

The notice does not tell users what to do, but the data it lists points to the order of work. Anything stored in a Fugaku or RIKYU home directory should be treated as copied:

  • SSH private keys, and the matching public keys removed from every server that trusts them;
  • access tokens for code hosting, container registries and cloud storage;
  • passwords or API keys written into job scripts and configuration files.

Replacing the key on the user's side is not enough if the old public key stays authorised elsewhere, which is the step most often missed. Organisations should also check the access logs of those outside services from 12 November onward for logins from addresses they do not recognise.

What RIKEN has yet to say

The notice leaves open how the intruder got in, whether the same access reached other RIKEN systems, and when Fugaku will run again. Projects with allocations ending this quarter have no guidance yet on lost compute time.

RIKEN says the investigation is continuing.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in