Ransomware · Cloud · Security · Backup

Ransomware takes down IDC Frontier's cloud (SoftBank): 495 Japanese organisations hit — a backup lesson for Vietnamese businesses

Last updated: 22 Oct 2026

Close-up of blade servers in a data centre rack, one unit pulled out, under cold blue light

Photo: panumas nikhomkhai / Pexels

In the early hours of 7 October 2026, IDCF Cloud — the cloud platform of IDC Frontier, a subsidiary of SoftBank Corp. in Japan — was hit by ransomware. According to IDC Frontier's own notices, 495 businesses and local governments using the affected region lost their virtual servers, and the provider stated that the data would be "difficult to retrieve or restore" — recoverable only from backups the customers kept themselves. The lesson for Vietnamese businesses is clear: renting cloud capacity does not mean you have a backup. If your only backup sits with the same provider, an incident like this can take both your systems and your data.

Quick summary

  • What happened: on 7 October 2026, at around 3:40 a.m. Japan time, the "East Japan Region 1" of IDCF Cloud went down; IDC Frontier confirmed the cause as a ransomware attack the same day.
  • Who was affected: 495 businesses and local governments with IDCF Cloud contracts; virtual servers in 4 availability zones were stopped and could not be restarted.
  • Data: the provider said data could only be restored from backups kept by customers; it later confirmed that 194 customers using the snapshot feature recovered their backups. As of the 18 October notice, the attacked zones had still not been restored.
  • The "7 minutes, 3.6 PB" figures are the attacker's own claims in the ransom message and have not been confirmed by IDC Frontier.
  • For Vietnamese businesses: keep at least one backup somewhere separate from your main cloud provider, that cannot be deleted, and rehearse restores regularly. The Ministry of Public Security's draft cloud standard already includes an "immutable backup" requirement.

Key figures (with sources)

What happened to IDCF Cloud?

This was a ransomware attack aimed directly at a cloud provider's infrastructure, not at individual customers. According to IDC Frontier's first report, the incident began "at around 3:40 a.m. on Wednesday, 7 October 2026", the scope was "East Japan Region 1", and the initial cause was "unauthorised access by a third party". The same day, the 2nd report confirmed it was a ransomware attack and said the company had disconnected the region from the network and shut the systems down "to prevent the spread of damage and data leakage".

IDC Frontier provides cloud infrastructure (IaaS) to Japanese businesses and public bodies. The 4th report says the company set up an emergency task force at 9 a.m. on 7 October and worked closely with its parent company, SoftBank Corp. Some international outlets wrongly named the parent as "SoftBank Group"; the official notices say SoftBank Corp.

Table 1 — Timeline based on IDC Frontier's official notices (Japan Standard Time, JST)
TimeEvent
7 Oct, ~03:40Incident begins in East Japan Region 1 (1st report)
7 Oct, 09:00Emergency task force set up, working with SoftBank Corp. (4th report)
7 OctRansomware confirmed; 495 customers affected; region disconnected from the network (2nd report)
8 Oct4 affected availability zones named; data "difficult to retrieve or restore"; customers advised to rebuild in another environment (3rd report)
14 OctNo sign that data inside virtual machines was exfiltrated; 194 snapshot customers recovered backups; 48 companies' portal information viewed without authorisation (5th report)
18 OctIDCF Cloud Backup service reopened; snapshot feature still suspended (6th report — latest as of 22 Oct)

How bad is the damage?

The main damage is to customers' servers and data in the attacked region. The 3rd report named 4 availability zones (tesla, henry, pascal, joule): virtual servers were stopped and could not be restarted, and customer data stored there "is expected to be difficult to retrieve or restore". The most important line in that notice: in the company's assessment at the time, data could only be restored from backups held by the customers themselves, and the company was guiding customers to prepare another environment to rebuild their systems. Other IDCF Cloud regions showed no sign of unauthorised access, but customers were still advised to back up their own data.

A week later, the picture was partly less grim. The 5th report said there was no trace of data inside virtual machines being viewed or taken out, and that 194 of the 495 customers — those who had enabled the snapshot feature — recovered their backup data, although whether each restore succeeds is still being discussed with customers individually. The same report confirmed that the registration details of 48 companies on the IDCF Cloud management portal were queried without authorisation; passwords were stored as hashes.

The damage spread to customers' customers. JR East warned that about 1.67 million Ekinet members and about 390,000 Otona no Kyujitsu Club members might have had their information exposed because its email delivery provider used IDCF Cloud; on 15 October, JR East said it had received a report that no personal information had been leaked, according to ScanNetSecurity.

Table 2 — Official information vs. the attacker's claims: don't mix them up
ClaimSourceReliability
495 customers affected; 4 availability zones stoppedIDC FrontierOfficial
194 customers recovered snapshot backups; 48 companies' portal information viewed without authorisationIDC FrontierOfficial
No data inside virtual machines taken outIDC Frontier (company's own assessment)Official, not independently verified
"Exactly seven minutes" to encrypt the whole regionRansom message, quoted by SDxCentralAttacker's claim, unconfirmed
Reached 239 hypervisors, encrypted 225 databases (SDxCentral says 225 data stores) totalling 3.6 PB, sealed 16,000 VM disks, wiped 554,153 snapshotsScreenshot of the ransom message, quoted by BleepingComputerAttacker's claim, not confirmed by IDC Frontier
How the attacker got in—Not disclosed

The shocking numbers need careful reading. SDxCentral quotes the attacker's message boasting: "Exactly seven minutes is what it took to turn your entire East Japan Region one into ciphertext (and) take a national cloud apart". BleepingComputer, citing a screenshot of the same message, reports: "The threat actor claims they encrypted 225 databases corresponding to 3.6 PB of data, reached 239 hypervisors, sealed 16,000 VM disks, and wiped 554,153 snapshots." BleepingComputer says "225 databases", while SDxCentral says 225 data stores. All of these are claims; so far no group has been named and IDC Frontier has not disclosed the entry point.

Two portable hard drives plugged into a laptop on a desk, illustrating offline backups
A backup held outside the cloud provider is what decides which customers can rebuild. Photo: Jakub Zerdzicki / Pexels

The biggest lesson: backups must be separate from the provider

The central lesson is this: a backup that sits with the same provider, on the same infrastructure, can be lost at the same moment as the main system. IDC Frontier said plainly that data could only be restored from backups customers kept themselves; customers with copies elsewhere were the ones in control of their own rebuild. Snapshots on the attacked platform itself helped 194 customers, but as of 18 October the feature was still suspended for safety checks — meaning customers were entirely dependent on the provider's timeline.

The industry is fairly aligned on the remedy, and Vietnam is writing it into standards. The draft national standard for cloud platforms serving critical digital infrastructure, published for comment by the Ministry of Public Security, requires that backups "must be stored in immutable write mode", and that no account — "including the highest-privileged account" — may delete, modify or overwrite a backup during its retention period. The draft also requires malware scanning before restore, clear disclosure of the maximum tolerable data loss (RPO) and maximum recovery time (RTO), and that the system must be able to keep operating "even in the event of losing access to the platform software provider". It is still a draft without an official number, but it shows where the regulator is heading.

For businesses, the practical principle boils down to this: at least one copy somewhere separate from your main provider (a different provider, on-premises, or offline), a copy that cannot be deleted with an ordinary admin account, and real restore drills — not just "backup is switched on".

Which rules apply in Vietnam?

For cloud serving e-Government, a requirements framework has existed since 2025. Decision 8297/QĐ-BCA-A05 of 9 October 2025 by the Ministry of Public Security issues a set of cybersecurity criteria for cloud computing platforms serving e-Government/e-local government. It is mandatory for state agencies and businesses providing cloud to e-Government; other organisations are encouraged to use it as a reference.

Table 3 — Selected requirements of Decision 8297/QĐ-BCA-A05 directly relevant to the IDC Frontier case
SectionRequirementRelevance to the IDC Frontier case
3.10Data backup and recovery in line with TCVN 14423, including for virtualised systemsCustomers without their own backups all but lost their data
3.16Report incidents to the National Cyber Security Centre within 24 hours of detection; maintain a disaster recovery plan, tested and updated at least once a yearThe recovery plan determines how long services stay down
3.3.2Allow customers to export all data (applications, configuration, metadata) securely and in a structured formCustomers were told to rebuild elsewhere — they need to get their data out
3.3.1e-Government data and encryption keys stored within VietnamControl over where data and keys reside
3.12Cybersecurity monitoring, with monitoring data shared with the National Cyber Security CentreEarly detection of abnormal activity on virtualisation infrastructure

One detail needs updating: Decision 8297 refers to TCVN 14423:2025, but on 24 July 2026, Quyết định 3243/QĐ-BKHCN (Decision 3243 of the Ministry of Science and Technology) published TCVN 14423:2026 "Cybersecurity – Information systems – Basic requirements" and repealed the 2025 version. We have not seen any amendment to Decision 8297 pointing to the new version.

At the statutory level, Luật An ninh mạng số 116/2025/QH15 (Cybersecurity Law No. 116/2025) (effective 1 July 2026) requires organisations to prepare a cybersecurity emergency response plan, to activate that plan immediately when an incident occurs, and to report to the specialised authorities. The law and Nghị định 333/2026/NĐ-CP (Decree 333/2026) also require domestic businesses to store certain types of user data in Vietnam — but that is a rule about storage location, not an obligation to back up or recover from disasters. Businesses should not read "our data is in the country" as "our data is safe".

What should Vietnamese businesses do now?

The first step is to answer one simple question: if your cloud provider went down tomorrow morning and never returned your data, where would you rebuild your systems from, and how long would it take? If the answer is "from a backup that also lives with that provider", you are in exactly the position many IDC Frontier customers were in on 7 October.

Table 4 — Action checklist (estimated effort for small and medium-sized businesses)
ActionPurposeTime (estimate)
List which systems run on which cloud, where the data lives and where the backups liveKnow who you depend on1–2 days
Add a backup in a separate location: another provider, an on-premises server, or offline drivesNot lost at the same time as the main system1 week
Enable deletion protection (immutability) on backups; separate backup admin accounts from operations accountsEven an attacker with admin rights cannot delete them1–3 days
Run a real restore drill for one critical system; record the time takenKnow your real RTO/RPO instead of guessing1 day/system
Review your cloud contract: recovery commitments, data export rights, liability in an incidentNot caught off guard when the provider has an incident1–2 days
Put an incident reporting process and response plan in place under the Cybersecurity LawMeet legal obligations and respond quickly1 week
Two IT staff staring intently at a computer screen in a dark room late at night, handling an incident
Regular restore drills reveal how long a rebuild really takes. Photo: Ron Lach / Pexels

Namtech perspective: concentration risk and internal AI

The IDC Frontier case shows concentration risk at work: one provider's incident drags down hundreds of organisations, then spreads to millions of their users. Cloud remains a sensible choice for many workloads, but businesses need to know exactly which parts of their operations depend on whom, and prepare a way out.

This is also why Namtech deploys internal AI on machines located right in the customer's office: data and models stay under the business's control, without depending on an external cloud platform. But on-premises does not mean immune — on-premises systems also need separate, undeletable backups and restore drills like any other system. Namtech builds backup and recovery into the design from the start of every deployment.

The ransomware attack on IDC Frontier's IDCF Cloud on 7 October 2026 left 495 Japanese businesses and local governments without their servers, and the provider confirmed that data could only be restored from backups customers kept themselves — proof that businesses need backups that are separate from their cloud provider, cannot be deleted, and have been tested in restore drills.

Frequently asked questions

What is IDC Frontier?

IDC Frontier is a cloud infrastructure and data centre provider in Japan and a subsidiary of SoftBank Corp. The service that was attacked is IDCF Cloud, East Japan Region 1. According to IDC Frontier, the IDCF Cloud TypeS and IDCF Private Cloud services were outside the scope of the incident.

Was customer data stolen?

According to IDC Frontier's 14 October report, the company found no trace of data inside customers' virtual machines being viewed or taken out, and assessed that there was no external leak. However, the registration details of 48 companies on the management portal were queried without authorisation. This is the company's own assessment; no independent party has published a verification.

Can the data be recovered?

On 8 October, IDC Frontier said data in the attacked zones would be difficult to retrieve or restore, and could only be restored from backups kept by customers. On 14 October, the company confirmed that 194 customers using the snapshot feature had recovered their backup data. On 18 October, the IDCF Cloud Backup service came back online, allowing restores to another cloud or to on-premises systems.

Are the "7 minutes" and "3.6 PB" figures accurate?

They are the attacker's own claims in the ransom message, quoted by SDxCentral and BleepingComputer. IDC Frontier has not confirmed these figures. The attacking group has not been named and the method of intrusion has not been disclosed.

Do Vietnamese businesses using cloud have to comply with Decision 8297?

Decision 8297/QĐ-BCA-A05 is mandatory for state agencies and businesses providing cloud to e-Government/e-local government. Other organisations are encouraged to use it as a reference. For all businesses, Cybersecurity Law 116/2025 requires an emergency response plan and incident reporting.

Is data hosted in Vietnam safer?

Not automatically. The data localisation rules under the Cybersecurity Law and Decree 333/2026 concern where data is stored, not backup or recovery. Wherever the data lives, businesses still need backups that are separate, cannot be deleted and have been tested in restore drills.

Review your business's backup and recovery plan

Namtech helps businesses inventory the systems they run in the cloud and on-premises, design separate, undeletable backups, and run restore drills so they know exactly how long it takes to rebuild when an incident strikes.

Book a free consultation

Note: This article is compiled from public sources checked on 22 October 2026, mainly IDC Frontier's official notices (in Japanese, translated by us). The situation is still developing and details may change. Figures claimed by the attacker are clearly marked as unconfirmed. The times in Table 4 are Namtech's estimates, not figures from the sources. The legal section is for reference only and does not replace legal advice.

Sources
Get started

Start with a free assessment

To define the right plan and detailed scope, Namtech offers a short, no-cost assessment session.

We reply within one business day. No spam, and we never share your details.