English edition · cyberattaques.org in FrenchFrançais
AttackIntrusion

Japanese cloud host Onamae Desktop Cloud confirms breach that planted malware on customer servers

Japanese cloud hosting provider Onamae Desktop Cloud has confirmed a cyberattack in which intruders compromised its infrastructure and installed malware on customer servers. More than 26,000 servers may be affected, putting organisations that host workloads with the provider at risk.

What to do now

Onamae Desktop Cloud, a cloud hosting provider based in Japan, has confirmed it suffered a cyberattack. According to Check Point Research's weekly threat intelligence report of 26 October 2026, the attackers gained access to the provider's infrastructure and used that position to install malware on servers belonging to its customers.

The potential scale is large, with more than 26,000 servers possibly affected. The source does not say what malware was deployed, how the attackers got in, how long they had access, or who is behind the attack. It also does not state whether customer data was stolen.

An attack at the hosting layer is hard for customers to defend against, because controls running inside each server may not stop code pushed from the underlying platform. Organisations using this service should treat their machines as potentially compromised until the provider and their own checks show otherwise.

The source does not describe the remediation steps announced by the provider. Affected customers should watch Onamae Desktop Cloud's official notices closely for indicators of compromise and specific instructions.

Action plan

What to do now

  1. If you use Onamae Desktop Cloud, list every server you host with the provider and review its official statements about the incident.
  2. Inspect those servers for unknown files, processes, scheduled tasks or accounts, treating each one as potentially compromised.
  3. As general good practice, rotate passwords, keys and access tokens stored on or used by those servers, working from a clean machine.
  4. Plan to restore or rebuild suspicious servers from verified backups taken before the incident once the provider's guidance is available.

Sources