---
title: "RIKEN Fugaku operational-network intrusion"
description: "RIKEN halted Fugaku after dashboard-linked unauthorized access and server tampering, with possible user-data exposure."
incident_type: "Data incident"
status: "active"
last_modified: "2026-11-19"
canonical_url: "https://www.ally.security/incidents/riken-fugaku-operational-network-intrusion-2026"
markdown_url: "https://www.ally.security/incidents/riken-fugaku-operational-network-intrusion-2026.md"
stix_url: "https://www.ally.security/incidents/riken-fugaku-operational-network-intrusion-2026/stix.json"
---

# RIKEN Fugaku operational-network intrusion

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

Last modified Nov 19, 2026 · 1 source

## 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

## What happened

[RIKEN](https://www.riken.jp/) reported unauthorized access to Fugaku’s operational network during November 10–13, 2026, followed by server tampering. [1](#source-1)

## Impact

Fugaku operations and queued jobs stopped; names, emails, user IDs and stored external-service credentials were taken or potentially taken. [1](#source-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](#source-1)

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

## Timeline

### November 12, 2026 — Suspicious traffic detected

RIKEN began investigating. [1](#source-1)

### November 14, 2026 — Operations suspended

Fugaku was taken offline. [1](#source-1)

### November 15, 2026 — Users notified

Users received incident emails. [1](#source-1)

### November 16, 2026 — Privacy regulator notified

RIKEN reported to the Personal Information Protection Commission. [1](#source-1)

### November 19, 2026 — 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](#source-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](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/riken-fugaku-operational-network-intrusion-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Possible personal information leak affecting Fugaku and RIKYU users

official · RIKEN · Nov 17, 2026

<https://www.riken.jp/en/news_pubs/news/2026/20261116_2/index.html>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Operations suspended: Fugaku was taken offline.
2. **Occurred At · 100% confidence · current**  
   Users notified: 2026-11-15
3. **Resulted In · 100% confidence · current**  
   Suspicious traffic detected: RIKEN began investigating.
4. **Occurred At · 100% confidence · current**  
   Suspicious traffic detected: 2026-11-12
5. **Affected Individual Count · 100% confidence · disputed**  
   Possible Fugaku user information exposure — conflicting reported limits: 4,222
6. **Occurred At · 100% confidence · current**  
   Privacy regulator notified: 2026-11-16
7. **Resulted In · 100% confidence · current**  
   Users notified: Users received incident emails.
8. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: RIKEN blocked external access, replaced administrative keys, invalidated user login keys and asked users to revoke credentials stored on Fugaku.
9. **Occurred At · 100% confidence · current**  
   Operations suspended: 2026-11-14
10. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: Fugaku operations and queued jobs stopped; names, emails, user IDs and stored external-service credentials were taken or potentially taken.
11. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: RIKEN reported unauthorized access to Fugaku’s operational network during November 10–13, 2026, followed by server tampering.
12. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: RIKEN found no evidence of research-data exfiltration but confirmed attempts to use obtained credentials against other systems.
13. **Resulted In · 100% confidence · current**  
   Privacy regulator notified: RIKEN reported to the Personal Information Protection Commission.
14. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: Access passed through a public operational-status dashboard; the exact intrusion method remained under investigation.
15. **Affected Organization · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: RIKEN
16. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: Users notified
17. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: Possible Fugaku user information exposure — conflicting reported limits
18. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: 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.
19. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: Operations suspended
20. **Affected Individual Count · 100% confidence · disputed**  
   Possible Fugaku user information exposure — conflicting reported limits: 4,224
21. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: Privacy regulator notified
22. **Resulted In · 100% confidence · current**  
   RIKEN Fugaku operational-network intrusion: Suspicious traffic detected

</details>
