Skip to content
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report
FrameFrame home

Your digital life. Back in your hands.

100% Canadian-owned · Support: support@frameprivacy.com

Product

  • Platform
  • Sample report
  • Breach Check
  • Frame agent
  • Extension
  • Mobile app
  • Pricing
  • Frame Business
  • Changelog

Resources

  • Blog
  • Help centre
  • Free leak test
  • Status
  • Data-broker catalog
  • RSS feed

Company

  • About
  • Our privacy promise
  • Contact
  • Press and brand

Legal

  • Legal hub
  • Privacy Policy
  • Terms
  • Security
  • Cookies
  • Accessibility

© 2026 Frame Labs Inc. All rights reserved.

en Englishfr Français
Your Privacy ChoicesSystem status

All posts

Breach · 5 min read

RIKEN says an intruder reached the Fugaku supercomputer and users’ stored keys

RIKEN says names, emails and user IDs for up to 4,597 people, plus SSH keys and other credentials users kept on Fugaku, were or may have been taken. It shut the system down on November 14.

BBy Brody · FramePublished November 17, 2026
The RIKEN logo on a light card with a dark blue edge, over a dark background.

RIKEN, the Japanese research institute that runs the Fugaku supercomputer, said on November 17, 2026 that an outsider got into the system’s internal operations network and took, or may have taken, information about its users. Its notice is the institute’s own account, and every detail below comes from it.

The people affected are researchers with accounts on Fugaku and on RIKYU, RIKEN’s AI for Science supercomputer. What makes this one different from a typical customer breach is the second kind of data: login keys and access keys that users had stored in their home directories to connect to other systems.

What happened, and when

RIKEN says the system involved helped operate Fugaku, and its maintenance was outsourced to an external service provider. The timeline it gives, in Japan time:

  • November 10 to 13: an outsider had access to Fugaku’s internal operations network. RIKEN says the way in was a publicly reachable web page that showed Fugaku’s operating status, the dashboard. The exact method is still under investigation.
  • November 12: suspicious network traffic was detected, and RIKEN started investigating with the provider.
  • November 13, 4:33 PM: unauthorized access was confirmed. At 10:07 PM the system used for the access was isolated.
  • November 14, 4:30 AM: Fugaku was shut down and outside access was blocked. Administrative keys were replaced that evening.
  • November 15, 4:18 PM: all running and queued jobs were stopped, users were emailed, and every user’s login public key was invalidated.
  • November 16, 5:55 PM: RIKEN reported the incident to Japan’s Personal Information Protection Commission. It had told the education ministry on November 13 and the HPCI organizations on November 15.

RIKEN says the intruder tampered with several internal servers, including by installing malicious programs, and it is still working out the details.

What was or may have been taken

The notice lists two groups of data.

From the user authentication system: names, email addresses and user IDs. RIKEN gives the total as up to 4,597 people: Fugaku users plus up to 375 RIKYU users, who had a name and email on file. The notice gives the Fugaku figure as up to 4,222 in one place and up to 4,224 in another; the total of 4,597 matches the first.

From users’ home directories: credentials that users stored there for connecting to systems and services outside RIKEN, such as SSH private keys and access keys, and the research files people kept. RIKEN says it has no evidence so far that research data or files left the system, and it is still checking whether any of those files held other people’s personal information.

RIKEN also says it has confirmed that the intruder tried to connect to other systems with some of the credentials it took. It is working with the relevant agencies to find out whether that caused any damage.

What RIKEN is asking users to do

For any SSH private key that was on Fugaku, RIKEN asks users to remove the matching public key from every outside service where it is authorized and to make a new key pair. Any other credential stored there should be revoked and replaced through the service it belongs to. It also warns about emails pretending to be from Fugaku or RIKEN, and says it will never ask for a password or personal information by email.

Fugaku stays offline until RIKEN rebuilds the compromised servers, fixes the software that was exploited, and reviews its network setup. It also says it will review how operations and maintenance duties are split with its provider, so it can respond faster next time.

What you can do

  1. If you stored keys or other credentials on Fugaku, treat each one as known to someone else. Changing the Fugaku password is not enough. If you only had a RIKYU account, RIKEN lists your name and email, not stored keys. Remove the old public key from GitHub, cloud accounts, university servers and anywhere else it was allowed in, then make a new pair.
  2. Revoke and reissue cloud access keys and API tokens, rather than only rotating a password. Check the provider’s logs for use you do not recognize, since RIKEN says the intruder tried some of the credentials elsewhere.
  3. Tell the owners of shared systems. If a key on Fugaku opened a lab or collaborator’s server, the people who run it need to know so they can check their own logs.
  4. Be careful with email about this incident. RIKEN says it will not ask for a password by email. Use the HPCI help desk address in the notice, not a link in a message.
  5. For the future, keep long-lived keys off shared machines where you can. A key with a passphrase, a short-lived token, or a key used only for one system limits what a single break-in can reach.

How Frame helps

If this breach is added to a catalog, add the affected address as a verified email in Frame and Frame shows what it exposed, gives you a short checklist and counts it in your exposure report. Frame can also look up your verified emails in Have I Been Pwned’s breach database. Frame does not hold SSH keys or cloud tokens, so the key steps above are ones you take with each service. Frame never collects or stores the leaked records themselves.

Related coverage

  • Railway’s final report: stolen AI keys ran up about $740,000 in charges: another incident where stored credentials were the prize, and what happened once they were used elsewhere.
  • Claude Code's "Don't Ask Again" file left passwords in 1,122 public GitHub copies: why keys kept in files on a machine travel further than people expect.

Sources

  • RIKEN, Notice regarding a possible personal information leak affecting Fugaku and RIKYU users following unauthorized access to the supercomputer Fugaku, November 17, 2026
  • Breaches
  • Guides
More in Breaches

More stories

  • BreachColes is investigating a cyber security incident and says it has found no data taken so farNovember 17, 2026 · 4 min read
  • BreachJINS says a vendor breach may include up to 18.29 million member accountsNovember 17, 2026 · 4 min read
  • BreachLegoland Korea says a reservation vendor may have exposed annual-pass detailsNovember 17, 2026 · 4 min read

New posts, by email.

About once a month. Plain-language privacy notes, nothing else. I never share your address.

Sent by Frame · privacy@frameprivacy.com · Privacy Policy

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report