RIKEN Fugaku operational-network intrusion

RIKEN halted Fugaku after dashboard-linked unauthorized access and server tampering, with possible user-data exposure.

Last modified

Summary

  • Environment: Fugaku supercomputer operational network
  • Operational impact: Compute jobs halted; user information and external-service credentials at risk
  • Financial impact: No confirmed incident cost quantified
  • Record status: Developing record. Reviewed November 19, 2026; updated as evidence emerges.

What happened

RIKEN reported unauthorized access to Fugaku’s operational network during November 10–13, 2026, followed by server tampering. [1]

Impact

Fugaku operations and queued jobs stopped; names, emails, user IDs and stored external-service credentials were taken or potentially taken. [1]

The notice gives conflicting Fugaku limits of 4,222 and 4,224 users, plus up to 375 RIKYU users; it also states 4,597 overall. These figures remain unresolved. [1]

RIKEN found no evidence of research-data exfiltration but confirmed attempts to use obtained credentials against other systems. [1]

Timeline

  1. Suspicious traffic detected

    RIKEN began investigating.

    [1]
  2. Operations suspended

    Fugaku was taken offline.

    [1]
  3. Users notified

    Users received incident emails.

    [1]
  4. Privacy regulator notified

    RIKEN reported to the Personal Information Protection Commission.

    [1]
  5. Briefing updated

    This briefing was last reviewed and updated on November 19, 2026.

Threat Group & Attack Vector

Access passed through a public operational-status dashboard; the exact intrusion method remained under investigation. [1]

Actors

  • No threat actor identity is established in the reviewed evidence.

TTPs

  • No specific MITRE ATT&CK technique is mapped for this case.

Response

RIKEN blocked external access, replaced administrative keys, invalidated user login keys and asked users to revoke credentials stored on Fugaku. [1]