Security Guides

RIKEN supercomputers Fugaku and Rikyu unauthorized access (up to 4,597 users): treated as a leak, 430 stored credentials collected — what users should do

RIKEN's second report treats the Fugaku and Rikyu access as a leak; traces of 430 stored SSH keys and credentials collected. What users should do.

Published 2026-11-17 Updated 2026-11-21 Last verified 2026-11-21 14 min read
On this page

For: users of the supercomputers Fugaku and Rikyu, and anyone who runs research computing environments. This article is based on RIKEN's official notice and does not cover attack techniques.

Developing: this article will be updated as the organisation publishes more

Who is affected

users of the supercomputers Fugaku and Rikyu, and anyone who runs research computing environments.

Confirmed so farSee the table ↓
  • Unauthorized access
  • Number of people
  • Traces of external connections
2 more
  • Tampering with servers
  • Reports

Listed as possibly affected

  • Stored files (research data)
Not yet confirmed
  • The specific method of intrusion (investigation committee)
  • Whether stored files contain third parties' personal information
  • Whether the traces of external connections involved any harm
1 more
  • When operation will resume
What to do nowSee the steps ↓
  1. Revoke the keys and credentials you stored on Fugaku, at the destination
  2. Check the destination logs for connections you do not recognize
  3. Take stock of the files in your home directory
2 more
  1. Do not open links in emails claiming to be from RIKEN or Fugaku
  2. RIKEN's email and where to ask
Last checked
As of November 20, 2026
Follow-up plans and what we checked

RIKEN says it will investigate the scope and cause in detail and "promptly announce" any new facts. On November 20 RIKEN published a second report saying it had identified traces of the intruder accessing the target information and is responding on the premise that a leak occurred (it has not confirmed external misuse). It will set up an investigation committee that includes outside experts, and will decide when to resume Fugaku after taking recurrence-prevention measures.

What Fugaku and Rikyu users should do today

1

Revoke the keys and credentials you stored on Fugaku, at the destination

RIKEN says the credentials users stored in their home directories for connecting to supercomputers and services outside RIKEN (SSH private keys, access keys and the like) were taken or may have been. It asks users to invalidate them at the connected service and reissue the keys or credentials they need.

Deleting a key on Fugaku does not stop a key that was already taken from working at the destination. The place to stop it is the destination. List the other universities' and institutes' supercomputers, cloud services and code-hosting services where you registered a public key or access key, remove the registration, and then create a new one (see SSH key least privilege).

2

Check the destination logs for connections you do not recognize

In its second report RIKEN says it confirmed traces of 430 credentials for connecting to external systems (233 private keys without a passphrase, 197 with one) being collected and moved from some users' home directories, and traces of external connections with some of the credentials. It has not confirmed any other misuse. It does not say which systems.

After revoking the keys, look at each destination's authentication log and usage history for connections you did not make since early November. If you find any, tell your organisation's security contact and the destination's operator. If you reused a key, every destination where it was registered is in scope.

3

Take stock of the files in your home directory

RIKEN says some of the files users stored (research data) were taken or may have been. It has not confirmed any specific fact showing that research results leaked, and is still checking whether the files contain third parties' personal information.

Check whether your home directory held participants' or collaborators' personal information, account details for other institutions, or data with sharing restrictions. If so, tell your organisation's security contact and your collaborators early.

4

Do not open links in emails claiming to be from RIKEN or Fugaku

The items RIKEN is responding to as leaked include names, email addresses and IDs and, per the second report, the information entered at account registration (address, affiliation, other attributes, contact details such as phone number). RIKEN urges caution about suspicious emails posing as Fugaku or RIKEN and says it does not ask for passwords or similar information by email.

If an email arrives about "re-registering your key" or "operation resumed", do not open the link; check on an official site you open yourself (see what is phishing).

5

RIKEN's email and where to ask

RIKEN says it emailed users at 4:18 p.m. on November 15 and invalidated all users' public keys for login. For questions, use the inquiry form (Public Relations Division, press contact) on RIKEN's notice page listed under Sources. Use the contact on the official site, not a link in an email.

What happened (from RIKEN's notice)

On November 16, 2026, RIKEN published a notice about possible personal information leakage due to unauthorized access to the supercomputers Fugaku and Rikyu. Everything below is based on that notice.

  1. November 10–13

    The investigation found that an outside third party had gained unauthorized access to the internal network of the operations system.
  2. November 12

    Detected suspicious communication and, working with the outside company that maintains the system, began investigating.
  3. November 13

    Confirmed the unauthorized access at 4:33 p.m. Reported to the Ministry of Education, Culture, Sports, Science and Technology at 8:59 p.m. and isolated the system used for the intrusion at 10:07 p.m.
  4. November 14

    Stopped Fugaku and cut off outside access at 4:30 a.m. Replaced administrative keys at 8:20 p.m.
  5. November 15

    Reported to the HPCI (High Performance Computing Infrastructure) related bodies at 10:51 a.m. At 4:18 p.m., emailed users, stopped all running and queued compute jobs and invalidated all users' public keys for login.
  6. November 16

    Reported to the Personal Information Protection Commission at 5:55 p.m. and published the notice.
  7. November 20

    Published a second report. Having identified traces of the intruder accessing the target information, it is responding on the premise that a leak occurred. Added the account-registration information and the identity-verification record; confirmed traces of 430 credentials collected and moved, and traces of external connections with some of them; will set up an investigation committee including outside experts.
Up to 4,597
People in the authentication-system information (Fugaku up to 4,222 + Rikyu up to 375)
2 kinds
Authentication-system information; home-directory files
Not confirmed
Specific fact showing research results leaked (as of Nov 16)
430
Credentials for external systems with traces of being collected and moved (233 private keys without a passphrase, 197 with)
Information taken or possibly taken (from RIKEN's notice)
Operator
RIKEN Center for Computational Science. Maintenance of the operations system is outsourced
Authentication-system information (first report: up to 4,597 people)
Name, email address and ID of Fugaku users (up to 4,222); name and email address of Rikyu users (up to 375). The second report gives 4,222 affected Fugaku users (no Rikyu figure)
Added in the second report
Information entered at account registration (address, affiliation, other attributes, contact details such as phone number). A record of identity verification (only the type of document used; leak of the identity documents themselves not confirmed)
Home-directory files
Credentials for connecting to supercomputers and services outside RIKEN (SSH private keys, access keys and the like). The second report confirms traces of 430 credentials for external systems (233 private keys without a passphrase, 197 with one) being collected and moved from some users' home directories. Files users had stored (research data)
Status of the data
First report: taken, or possibly taken. Second report: having identified traces of the intruder accessing the target information, RIKEN is responding on the premise that a leak occurred, while external misuse is not confirmed. No specific fact showing research results leaked had been confirmed as of November 16
Traces of external connections (second report)
Traces of external connections with some of the credentials have been confirmed; no other misuse has been confirmed. Affected users are contacted individually and asked to revoke and reissue keys at the destinations
Investigation (second report)
An investigation committee including outside experts will be set up
Effect on systems
Confirmed that some of the intruded servers had been tampered with, such as by installing unauthorized programs
What was stopped
Fugaku operation; all running and queued compute jobs; all users' public keys for login
Resumption
To be decided after recurrence-prevention measures (separating the public-facing service from the management network, rebuilding servers and the like). No date given

What is known and what is not

Based on RIKEN's November 16 first report and November 20 second report, as of November 20, 2026. We will update the status column when follow-ups come out.

ItemWhat the notice saysStatus
Unauthorized accessOccurred November 12, confirmed November 13; the intrusion was between November 10 and 13Confirmed
Authentication-system informationNames, email addresses, IDs (Fugaku); names, email addresses (Rikyu). The second report says traces of the intruder accessing the target information were identified and RIKEN is responding on the premise that a leak occurredResponding on the premise of a leak (RIKEN; external misuse not confirmed)
Account-registration information and identity-verification record (second report)Address, affiliation, other attributes, contact details such as phone number. Identity verification is only the type of document used; leak of the documents themselves not confirmedResponding on the premise of a leak (RIKEN)
Number of peopleFirst report: up to 4,222 registered Fugaku users and up to 375 registered Rikyu users; up to 4,597 in total. Second report: 4,222 Fugaku users whose information may have leaked (no Rikyu figure)Confirmed (maximum)
Stored credentials (SSH private keys, access keys and the like)Second report: traces of 430 credentials for external systems (233 private keys without a passphrase, 197 with one) collected and moved from some users' home directories. Users asked to revoke at the destination and reissueTraces confirmed (RIKEN)
Stored files (research data)Taken, or possibly taken (first report). No specific fact showing research results leaked as of November 16Possible (RIKEN)
Whether files contain third parties' personal informationBeing checkedUnder investigation
PasswordsNot listed among leaked itemsNot stated
Traces of external connectionsSecond report: traces of external connections with some of the credentials confirmed; no other misuse confirmed (the first report said attempts to connect to other systems with some credentials obtained were confirmed)Confirmed (traces); harm under investigation
Tampering with serversUnauthorized programs installed on some servers, among other changesConfirmed
Specific method of intrusionSays an internet-exposed page showing operating status was the foothold; the specific method is under investigationUnder investigation
Misuse of the informationNot statedNot stated
Investigation committeeWill be set up, including outside experts (second report)Announced (RIKEN)
Resumption of operationTo be decided after recurrence-prevention measures (separating the public-facing service from the management network, rebuilding servers and the like); no date givenUnder investigation
ReportsPersonal Information Protection Commission, the Ministry of Education, Culture, Sports, Science and Technology, and HPCI related bodiesConfirmed

What 'traces of external connections' means

In its second report RIKEN says it confirmed traces of external connections with some of the credentials (the first report said some of the credentials obtained were used in attempts to connect to other systems). The notice does not say whether any attempt succeeded or which systems were involved.

So whether your key was used is something you can only find out from the logs at the destinations. Do not wait for RIKEN; revoke the keys and check those logs first.

What names, emails and connection keys together can enable

The following is what generally follows from this combination of items. It does not mean any of it has happened here.

  • Private keys and access keys: the key itself is the way in to the destination. If a key not protected by a passphrase is taken, whoever has it can try to connect, as you, to any service where it is registered. That is why you revoke it at the destination.
  • Name + email address + ID (+ registered address, affiliation, phone number): someone who knows your affiliation and the systems you use can write a convincing email posing as a colleague or operator, for example one telling you to "re-register your key" and pointing to a fake site.
  • Research data: for data involving collaborators, participants or unpublished work, a leak affects trust in the research and the protection of personal information. RIKEN is still checking whether third parties' personal information is included.

For people who run research computing environments

These are points from RIKEN's account that other environments can review. The detailed cause has not been published, so we do not guess at the method and stay within what is disclosed.

1

Do not leave keys stored in home directories to users alone

According to RIKEN, the information taken or possibly taken includes credentials that users kept in Fugaku home directories for connecting to other institutions and services. Users storing keys is not unusual, but when one computing environment is compromised, the destinations beyond it are affected too.

Set rules for where keys are kept (passphrases required, time-limited keys, restricting where they can be used from) and tell users. See SSH key least privilege and the basics of env vars and API keys.

2

Inventory what you expose to the internet, and close anything connected to the operations side

RIKEN says an internet-exposed page showing operating status was the foothold into the operations system's internal network. Even a supporting screen such as a status display should not be reachable by anyone on the internet if it connects to the operations side. If it must be public, make it a display-only environment separated from the operations side.

3

Decide beforehand how users will be asked to revoke keys

RIKEN says it stopped Fugaku on November 14, two days after detection, and at 4:18 p.m. on November 15 invalidated all users' public keys and emailed users at the same time. Deciding the order and owners in advance (revoking keys, telling users, stopping running jobs) reduces hesitation. RIKEN says it will promptly review the division of roles in its operations and maintenance setup so it can respond faster in an emergency.

Sources (public record)

The facts in this article are based on the public information below. We have not speculated about the method of intrusion or the cause, which have not been disclosed.

  • RIKEN, notice on possible personal information leakage due to unauthorized access to the supercomputers Fugaku and Rikyu (November 16, 2026; Japanese) — riken.jp
  • RIKEN, report on the investigation into unauthorized access to the supercomputers Fugaku and Rikyu (second report) (November 20, 2026; Japanese) — riken.jp

Update history

2026-11-20: Reflected RIKEN's second report (November 20). Having identified traces of the intruder accessing the target information, RIKEN now responds on the premise that a leak occurred. Account-registration information and an identity-verification record were added; traces of 430 external-system credentials collected and moved, and traces of external connections with some of them, were confirmed. An investigation committee including outside experts will be set up, and resumption will be decided after recurrence-prevention measures.

2026-11-17: First version, based on RIKEN's November 16 notice. RIKEN is investigating the scope and cause and says it will promptly announce new facts. We will update this article when it does.

Latest breaking reports

All breaking reports →

FAQ

QWhat was leaked in the Fugaku and Rikyu unauthorized access?
A

According to RIKEN's notice of November 16, 2026 and second report of November 20, RIKEN is responding on the premise that a leak occurred, although it has not confirmed external misuse. What is covered is the information registered in the users' authentication system (name, email address, ID; the second report adds the information entered at account registration (address, affiliation, other attributes, contact details such as phone number) and a record of identity verification that holds only the type of document used, with no leak of the documents themselves confirmed) and some files in users' home directories. The latter include credentials for connecting to supercomputers and services outside RIKEN (SSH private keys, access keys and the like) and files users had stored (research data).

QHow do I know whether I am affected?
A

The users who may be affected are up to 4,222 registered Fugaku users and up to 375 registered Rikyu users; the authentication-system information covers up to 4,597 people in total. RIKEN says it emailed users at 4:18 p.m. on November 15. Its November 20 second report gives 4,222 affected Fugaku users (it gives no Rikyu figure) and says it will contact the affected users individually. If you use Fugaku or Rikyu and did not receive that email, ask RIKEN through the inquiry form at the bottom of its notice.

QWere passwords leaked?
A

Passwords are not listed among the leaked items in the notice, which lists names, email addresses, IDs and home-directory files. We cannot say that something not listed was not leaked, but the stored credentials include SSH private keys and access keys, so revoking and reissuing those comes first.

QWhat was the cause?
A

RIKEN says an outside third party got into the internal network of the operations system between November 10 and 13, using an internet-exposed web page that showed Fugaku's operating status as a foothold. The specific method is still under investigation, and it lists dealing with the abused software vulnerability among the steps before resuming operation (the second report adds separating the public-facing service from the management network and rebuilding servers, and says an investigation committee including outside experts will be set up). It also says maintenance of the operations system is outsourced.

QWhat if I get a message claiming to be from RIKEN?
A

RIKEN urges caution about suspicious emails posing as Fugaku or RIKEN, and says it never asks for passwords or similar information by email. Do not open links in such emails; check through an official site you open yourself or your usual contact.

QWhen will Fugaku be available again?
A

The notice gives no date. RIKEN says it will resume operation after taking recurrence-prevention measures, including dealing with the abused software vulnerability, rebuilding the intruded servers and reviewing the network configuration. All running and queued compute jobs were stopped at 4:18 p.m. on November 15.