Protect.Computer
NEWS

RIKEN Takes Fugaku Supercomputer Offline After Breach

· 2 min read · Got hacked Network safety
RIKEN Takes Fugaku Supercomputer Offline After Breach

RIKEN, the Japanese research institute that runs the Fugaku supercomputer, has taken the machine offline after unauthorized access to its operations systems. In a notice dated November 16, RIKEN says it detected suspicious communication on November 12 and confirmed the intrusion on November 13 at 4:33 pm. It stopped Fugaku at 4:30 am on November 14 and cut off outside access. The investigation found the intruder was inside the internal network between November 10 and 13, using Fugaku’s public status dashboard as a foothold; RIKEN says the exact method is still under investigation. Maintenance of the affected system is outsourced, and RIKEN says it will review how responsibilities are split for faster emergency response.

According to RIKEN, the intruder operated multiple internal servers and tampered with some of them, including installing unauthorized programs. Data taken, or possibly taken, includes names, email addresses and IDs from the user authentication system for up to 4,222 Fugaku users and names and email addresses for up to 375 users of Rikyu, a separate AI-for-science supercomputer. It also includes files from users’ home directories, among them SSH private keys, access keys and other credentials for supercomputers and services outside RIKEN, plus research data files. RIKEN says it has not confirmed that research results left the building, is still checking whether the files contain third-party personal information, and has seen the intruder try some of the stolen credentials against other systems. It is investigating whether that caused secondary damage. BleepingComputer, which reported the story on November 17, says RIKEN has not attributed the attack.

How to check if you’re affected

Affected products are accounts on Fugaku and Rikyu: RIKEN says up to 4,222 and 375 registered users respectively may be affected, and it emailed users on November 15. RIKEN invalidated every user’s login public key that day, stopped all running and queued jobs, and asked users to do the following:

  • Revoke any SSH private keys and other credentials that were stored on Fugaku at the services they connect to, and issue new ones.
  • Watch for suspicious emails that impersonate Fugaku or RIKEN. RIKEN says it never asks for passwords by email.

RIKEN says Fugaku will resume only after it has fixed the exploited software vulnerability, rebuilt the compromised servers and reviewed the network configuration, and that it will publish new findings promptly.

Sources

Related reading