JETPLAIN / FIELD NOTES / 001
← Cyber Security & Privacy

BY JETPLAIN /

Japan's Fugaku Supercomputer Was Breached. Here's What We Know.

What RIKEN has confirmed about the November 2026 intrusion, the exposed credentials, and the questions still unanswered.

A supercomputer is very good at doing an enormous amount of math. That does not mean every web dashboard connected to its operations is automatically secure.

Japan's research institute RIKEN has confirmed unauthorized access to systems supporting Fugaku, its flagship supercomputer. The incident is real. Some of the more dramatic explanations circulating online are not yet supported by evidence.

This is a developing report based on RIKEN's November 17 English-language notice. No Jetplain hands-on investigation or independent forensic test has been performed.

FIELD NOTES / 01

What RIKEN confirmed

  • RIKEN detected suspicious network traffic on November 12, 2026, and confirmed unauthorized access on November 13.
  • Investigators identified activity from November 10 through November 13. Attackers entered the operational network through a publicly accessible system-status dashboard. The precise flaw or method remains under investigation.
  • Multiple internal servers were tampered with, including the installation of malicious programs.
  • Information in the authentication system and files in user home directories may have been exposed or removed. This included names, email addresses, user IDs and potentially SSH private keys or other credentials users had stored for external services.
  • Investigators confirmed attempts to use some obtained credentials to access other systems. Resulting secondary damage had not been established at the time of the notice.
  • Fugaku operations were halted and outside access blocked at 4:30 a.m. on November 14. RIKEN disabled login keys, notified users and began remediation.

Read RIKEN's original incident notice.

FIELD NOTES / 02

How many people could be affected?

RIKEN's announcement describes roughly 4,600 potentially affected users across Fugaku and the related RIKYU AI-for-science system. Its English notice contains a small numerical inconsistency: the opening lists up to 4,222 Fugaku users and 375 RIKYU users, while a later section lists 4,224 Fugaku users alongside the same 375 RIKYU users but gives 4,597 as the combined total. The exact affected count needs clarification rather than a confidently repeated headline number.

FIELD NOTES / 03

What has not been established

  • The identity, location, affiliation or motive of the attackers.
  • The precise vulnerability exploited in the public-facing dashboard.
  • Whether research datasets were stolen. RIKEN says it has no evidence of research-data exfiltration at the time of its statement.
  • Whether the attackers succeeded in accessing outside systems with the credentials they obtained.
  • Whether AI agents or autonomous hacking tools were involved. There is no disclosed evidence connecting this intrusion to an AI-driven campaign.

Those unknowns are not footnotes. They are the boundary between reporting and guessing.

FIELD NOTES / 04

Why a status dashboard matters

A status page sounds harmless: show whether compute jobs or systems are running, then go home. But if a public-facing interface has an unexpected path into operational infrastructure, an attacker may be able to cross a security boundary that should have been tightly controlled.

That is the engineering question worth examining here: how did an internet-accessible status page become a route toward internal administrative systems? We do not yet know the implementation detail, so assigning a particular vulnerability would be speculation.

The next critical question is credential reuse. An attacker who finds a private SSH key or API token on one system may try that credential elsewhere. RIKEN confirmed that such attempts occurred.

FIELD NOTES / 05

What affected users should do

RIKEN instructed Fugaku users to revoke and replace any SSH keys and other authentication credentials stored on Fugaku. In practice, that means removing the compromised key's authorization from the external services where it was trusted, generating a replacement key pair and following each service's token-revocation instructions.

RIKEN also warns users about phishing emails that pretend to come from the institution. It says it will never ask for passwords or personal information by email.

People who have never used Fugaku or RIKYU have no reason, from this disclosure alone, to assume their own accounts were breached.

FIELD NOTES / 06

Fifteen-minute security lesson: the trust boundary

You do not need a supercomputer to understand the security principle.

  • Minutes 0–5: Sketch three boxes: public web status page, internal operations network and user credential store.
  • Minutes 5–10: Draw the trust boundaries. Mark which systems should be able to talk to which others and with what permissions.
  • Minutes 10–15: List questions an investigator would ask: What logs exist? Which accounts and services were touched? Were credentials reused? What changed on the servers?

That is an exercise in reasoning, not a tested reconstruction of the Fugaku breach.

FIELD NOTES / 07

What we will watch next

We will look for official updates on the entry mechanism, affected records, confirmation or exclusion of research-data theft, credential misuse, and recovery of computing operations. Any new attribution or AI involvement must be supported by evidence, not just timing or social-media chatter.

FIELD NOTES / 08

Sources and verification

Sources checked November 17, 2026. This article is a research summary, not a forensic report or a claim that Jetplain independently validated the incident.

Back to the Field Guide