Fugaku Supercomputer Cyberattack: RIKEN Confirms Unauthorized Access and Service Suspension

当ページのリンクには広告が含まれています。
Editorial illustration of a supercomputer facility with a cybersecurity warning, labeled Fugaku Security Incident, November 2026
ノートンストア

Updated November 16, 2026 (Japan Standard Time). Japan’s RIKEN research institute has confirmed unauthorized access to a system associated with Fugaku, the supercomputer it operates in Kobe. Access and operations have been suspended as investigators examine the scope of the incident. Potential exposure of user information, research files and authentication material remains under investigation; a confirmed breach of every user’s data has not been established.

If you use Fugaku or administer a research environment connected to it, the immediate priorities are to verify operator notifications through trusted channels, identify credentials and data that might be at risk, and prepare coordinated key rotation and integrity checks. Do not assume that a social media screenshot proves what was stolen.

Fugaku Security Incident, November 2026: editorial illustration of server racks with a cybersecurity warning
Illustration created for this article; not an actual image of the cyber incident.
広告・PR
目次

What is confirmed—and what remains unknown

QuestionStatus as of November 16
Was there unauthorized access?Confirmed. RIKEN acknowledged an incident affecting a related/operational system when contacted by Japanese news organizations.
Is Fugaku available?Operations suspended. News reports describe a service shutdown; RIKEN’s own operating-status page says it is unavailable for security reasons.
Were users notified?Yes. RIKEN confirmed it sent emails to users.
Were files, SSH keys or credentials stolen?Not established. These concerns appear in reports of a user notification, but RIKEN told ITmedia that the reported details were still being checked.
Which machines or users were affected?Undetermined. The confirmed boundary of the affected system, number of users and extent of any exposure have not been published.
When will Fugaku resume service?No confirmed restart date. The operator is investigating.

The distinction matters: an intrusion into a system used to connect to or operate a supercomputer does not, by itself, establish that an attacker gained unrestricted control of its compute nodes, stole every research dataset or altered all submitted jobs. ITmedia NEWS reported RIKEN’s November 16 confirmation and its explicit uncertainty about the alleged leaked files and credentials. FNN and TV Asahi also reported the suspension and ongoing investigation.

Fugaku incident timeline: November 13–16, 2026

Date (JST)What has been reportedEvidence level
Nov. 13Japan’s Ministry of Education, Culture, Sports, Science and Technology (MEXT) had received a report by this date, according to a Yomiuri Shimbun report.Attributed to a news report
Nov. 14, 04:30External access was blocked from this time, according to Mainichi Shimbun reporting.Attributed to a news report
Nov. 15Users were sent an incident notice; text described as the notification began circulating online.Email distribution confirmed by RIKEN; contents require caution
Nov. 16RIKEN publicly acknowledged unauthorized access when questioned by journalists. Operations remained suspended; investigation continued.Confirmed in multiple reports

A Mainichi Shimbun report says the user notification raised the possibility of accessed files, compromised login material and altered programs, and advised checking results of jobs run between November 12 and 15. Those statements are reported descriptions of a notification—not a completed forensic assessment. RIKEN had not confirmed the precise impact in the material we reviewed.

What was attacked: access systems, not necessarily the entire supercomputer

Fugaku is operated by the RIKEN Center for Computational Science (R-CCS). It supports Japanese and international research as well as industrial projects. Its official architecture overview describes a large distributed computing environment, shared storage layers and specialized infrastructure.

According to RIKEN’s Fugaku Startup Guide, version 1.11, users access the website with a client certificate and authenticate to login nodes using SSH public-key authentication. The user generates a key pair on their own device and registers the public key with the service; the private key should remain protected on the user device. The guide also documents login and file-transfer workflows.

Simplified access and security boundary

ComponentNormal purposeWhat an administrator should assess
Researcher workstationStores client certificates, SSH private keys and local project files.Check whether credentials were shared or reused elsewhere; inspect local security alerts.
Fugaku website / access servicesIdentity, certificate and account-access functions.Wait for operator guidance on any credential or certificate replacement.
Login and file-transfer nodesAuthenticated entry to development, submission and data movement workflows.Identify associated public keys, user accounts, submitted scripts and transfers.
Compute jobs and storageScientific workloads, outputs, home and shared project data.Inventory sensitive files; validate data and job results if a notice calls for it.

Architecture illustration in table form, not a reconstruction of the attack path. The intrusion vector and whether these components were compromised have not been established.

Why possible SSH-key or credential exposure matters

An SSH private key is an authentication secret. If an attacker obtained a usable private key—and any additional passphrase or required access conditions—an attacker might be able to impersonate its owner on systems that trust the corresponding public key. Possession of a public key alone normally does not grant the same access. The incident does not prove that users’ private keys were stored on Fugaku or stolen.

A home directory may also hold job scripts, configuration files, environment variables, API tokens or unpublished datasets depending on user practice. A report that files may have been read therefore deserves investigation, but it is not proof that every directory contained secrets or that exfiltration occurred. Similarly, unauthorized modification of a job script could jeopardize scientific reproducibility; whether that happened here is unconfirmed.

Action checklist for Fugaku users and research IT teams

1. Verify incident instructions using a trusted channel

Confirm the sender and exact instructions with your institution’s HPC administrator or RIKEN’s official user-support contacts. Avoid logging in from links in forwarded emails or screenshots. With access suspended, do not repeatedly test unavailable endpoints or bypass restrictions.

2. Inventory credentials and affected systems

List the SSH public keys registered to Fugaku, their corresponding private-key locations, relevant client certificates and any passwords or API tokens used by research automation. Distinguish keys held only on your workstation from credentials copied into scripts, shared folders or remote home directories. Check whether the same key pair or secret is trusted by other research servers, cloud VMs or Git platforms.

3. Prepare rotation, but coordinate execution

If a private key or token could have been exposed, arrange a replacement credential and revoke the old access wherever it is trusted. Remove old authorized public keys on other systems you control when replacing a compromised key. Follow the operator’s procedure for changing Fugaku-side registrations once service permits; avoid deleting the only working access path before a replacement is ready. Use unique passphrases and do not email private keys.

4. Check for unusual access and preserve evidence

On systems your organization controls, review SSH authentication events, cloud access logs, SSO records, credential usage, unexpected transfers and privileged changes for a defensible period around the incident. Preserve timestamps and relevant records. Absence of alerts does not rule out an incident, especially if logs are incomplete.

5. Identify exposed research data and validate results

Determine which research datasets, customer or partner information, simulation inputs and outputs, scripts and configuration files were present on Fugaku. Classify their sensitivity and identify contractual or disclosure obligations if exposure is established. Where relevant, recheck numerical outputs using trusted inputs or reproducible execution records. The reporting about a November 12–15 recheck is attributed to a circulated notification; seek direct guidance from the operator before treating that window as a verified compromise period.

6. Coordinate communications and incident decisions

Assign an owner for RIKEN updates, document what is confirmed versus suspected, and record when keys or certificates are replaced. For joint projects, alert project information-security contacts without asserting a leak that has not been verified. Escalate potential regulatory reporting according to the type of data and applicable jurisdiction.

Frequently asked questions

Was the Fugaku supercomputer itself hacked?

RIKEN confirmed unauthorized access to a system associated with or used to operate/access Fugaku. Public reporting has not established that attackers gained direct control of every compute node. The exact intrusion boundary remains under investigation.

Have all Fugaku users’ private SSH keys been leaked?

No such blanket conclusion is supported by confirmed findings. Reports describing a user notice raised concern about authentication material and possibly broad impact, but RIKEN told ITmedia it was checking those details. Also, under Fugaku’s documented setup, private keys are generated on users’ own devices rather than uploaded during ordinary public-key registration.

Does a service outage mean research data has been deleted or stolen?

No. Suspending access is a containment measure and does not, by itself, prove data loss or exfiltration. Data theft and integrity changes are separate forensic questions that require evidence.

When will Fugaku be back online?

A verified restoration date was not available in the sources checked on November 16, 2026. Follow RIKEN’s operating-status page and official user communications for updates.

Should I rotate credentials immediately?

Evaluate credentials with your security team now, prioritize any key or token that was copied to potentially exposed locations or reused elsewhere, and coordinate changes on Fugaku itself with the operator. This is precautionary guidance, not an assertion that every key has been compromised.

Sources and verification notes

Verification date: November 16, 2026, Japan Standard Time. At the time of this check, a standalone official incident report detailing the root cause and affected records was not identified; this story therefore attributes incident-specific claims to interviews and contemporaneous reporting, while using RIKEN’s official publications for system background. We will distinguish any later forensic findings from the initial reports.

よかったらシェアしてね!
  • URLをコピーしました!
  • URLをコピーしました!

この記事を書いた人

はじめまして、「ぴろりん」です。
このブログでは、IT運用管理・PC修理・情報セキュリティ対応・資格学習など、実務で直面した課題とその解決策を発信しています。
同じような悩みを抱える方のお役に立てれば幸いです。

目次