CVE Index中文
L4 · Septic Tank Blewhpc · data-breach · credential-theftriken-fugaku-intrusion

RIKEN confirms Fugaku intrusion and downstream credential abuse attempts

RIKEN says an intruder used Fugaku’s public status dashboard as a foothold into its operations network. Authentication records for up to 4,597 Fugaku and Rikyu users may have been exposed. The intruder used some obtained credentials to attempt access to other systems.

Disclosed
Nov 16, 2026
Public disclosure date
Severity
Septic Tank Blew
No CVE: a breach, not a bug
Splash zone
Up to 4,222 Fugaku and 375 Rikyu users, plus external services whose credentials were stored on Fugaku.
hpc · data-breach · credential-theft
In the wild
Yes
RIKEN confirmed intrusion, server tampering and attempts to reuse stolen credentials.

What happened

RIKEN’s Center for Computational Science confirmed unauthorized access to Fugaku’s operations network. The intruder used the public operating-status dashboard as a foothold, manipulated multiple internal servers and installed unauthorized software on some of them. RIKEN was investigating the exact entry method. Its announcement did not identify a product version or CVE.

The potentially exposed authentication records comprise names, email addresses and user IDs for up to 4,222 Fugaku users, and names and email addresses for up to 375 Rikyu users. Fugaku home-directory files were also in scope, including research files and SSH private keys or access keys for external systems. RIKEN had found no specific evidence that research outcomes left its systems and was checking whether the files contained third-party personal information. Attempts to use obtained credentials on other systems were confirmed. Whether those attempts caused further compromise remains under investigation.

RIKEN plans to address the abused software vulnerability, rebuild compromised servers and revise the network configuration before resuming Fugaku operations. The login keys RIKEN invalidated controlled access to Fugaku. Keys and other credentials stored on Fugaku for use elsewhere must be revoked by the destination operators or their users.

Crime-scene timeline

  1. Nov 10, 2026

    Intrusion window begins

    RIKEN traced activity from November 10 through November 13 to a foothold on the public status dashboard.

  2. Nov 12, 2026

    RIKEN detects suspicious network traffic

    RIKEN began investigating with its maintenance contractor.

  3. Nov 13, 2026

    RIKEN confirms the intrusion and isolates the system used to gain entry

  4. Nov 14, 2026

    RIKEN takes Fugaku offline

    RIKEN cut external access and replaced administrative keys.

  5. Nov 15, 2026

    Users are notified and existing login public keys are invalidated

    RIKEN notified users, stopped all running and queued jobs, and asked users to revoke credentials stored on Fugaku at their destinations.

  6. Nov 16, 2026

    RIKEN discloses the incident and possible exposure

    RIKEN published the potential scope and confirmed attempts to reuse obtained credentials. The entry method and downstream impact were still under investigation.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.