FirstVDS Cyberattack: How a VMmanager 6 Vulnerability Exposed Customer Data
Attackers reportedly used a VMmanager 6 vulnerability to copy customer data while the servers kept running normally. Here is what was exposed and what to do next.
A flaw in VMmanager 6, the virtual machine management platform, let attackers to gain access to a portion of the virtualization infrastructure of Russian hosting company FirstVDS on October 17, 2026. A data-stealing malware connected certain customers’ virtual disks in read-only mode and transferred private files to a server under the attacker’s control as part of the FirstVDS cyberattack. The compromised virtual private servers continued to operate, and there were no overt indications of theft within their guest operating system. The incident is detailed in The Record’s report.
What happened in the FirstVDS cyberattack?
FirstVDS said only part of its infrastructure was affected. It notified customers whose servers were identified as exposed and advised them to treat data on those servers as copied. The company has not disclosed a total number of affected customers or servers.
VMmanager 6 is virtualization management software developed by ISPsystem. On 20 October, the vendor confirmed a security incident involving a vulnerability in one build, but did not identify affected operators or disclose the entry method. No public CVE identifier was included in the statements reviewed. The FirstVDS cyberattack remains a confirmed infrastructure-level incident, but the exploit chain is not public. The public statements do not describe the VMmanager 6 vulnerability at code level.
In its 21 October update, FirstVDS said its technical review was complete and additional customers had been notified. Its official incident updates detail the response. FirstVDS also reported hidden services on some infrastructure nodes that could have restored attacker access. Those nodes were being cleaned and checked before return to service. Although the vendor reportedly said the flaw was closed, the panel remained isolated during remediation and verification.
How the VMmanager 6 Vulnerability Was Exploited
Rather than needing malware inside each customer’s operating system, the data collector reportedly ran from the hosting infrastructure. It mounted virtual disks read-only, searched their contents and sent collected information outside the provider’s network. Files and services can remain unchanged even after data has been copied; normal uptime does not prove confidentiality.
The VMmanager 6 vulnerability affected a management layer with reach across multiple virtual machines. A control-plane weakness can expose several tenants even when guest systems appear normal. ISPsystem’s security statement does not disclose the exploit chain, so the VMmanager 6 vulnerability should not be assigned a specific method without evidence.
What data was at risk in the FirstVDS data breach?
FirstVDS said the collector copied passwords, SSH keys, API keys, cloud credentials and access tokens, along with configuration files, command history, cryptocurrency wallet files and other files. The FirstVDS data breach should be treated as possible credential exposure, not just a service-availability incident.
Environment files may contain database strings, cloud keys, source-control tokens and CI/CD secrets. The FirstVDS data breach does not prove every category was present on every server, so customers should treat data on notified servers as exposed. Because no total was published, its confirmed scope remains specific to servers identified by the provider.
The FirstVDS data breach may have consequences beyond the affected VM: copied credentials can remain useful after the original access path is closed. An attacker could try a cloud key or database password on another system, where activity may not appear in the VPS logs.
Why the FirstVDS cyberattack may leave no local trace
little to observe. Clean guest logs cannot rule out theft at the hypervisor layer. FirstVDS also reported persistence mechanisms on some infrastructure nodes, making host validation and removal of unauthorized access paths part of recovery.
The FirstVDS cyberattack does not mean every customer was breached. FirstVDS said it notified customers whose servers were identified as affected; individual status should be based on the provider’s notice.
What affected customers should do
If FirstVDS notified you that a server was affected, treat the FirstVDS cyberattack as exposure of every secret stored on it:
Rotate credentials from a clean device. Change root and user passwords, database logins, website administrator accounts, email credentials and other stored secrets.
Revoke keys and tokens. Revoke old SSH keys, cloud keys, API tokens, source-control credentials and CI/CD secrets before issuing replacements. Do not leave old keys active.
Review connected services. Check cloud consoles, source-control platforms, deployment systems, databases and payment services for unfamiliar logins, new keys or unusual activity after 17 October.
Inspect for persistence. Review authentication logs, authorized SSH keys, new users, cron jobs and systemd services.
Secure wallet material. If private keys or recovery phrases were stored on the disk, treat them as compromised and move assets to a newly generated wallet from a secure device.
Confirm scope. Ask your provider whether its management plane or host nodes were exposed and which remediation steps apply.
What hosting operators should learn
Providers should treat the management plane as a high-value security boundary: restrict public access, enforce strong administrator authentication, separate control systems from tenant workloads, and monitor unusual disk mounts and outbound transfers. They need a tested process to identify and notify affected tenants. Customers should limit permissions and avoid long-lived secrets in configuration files. Short-lived, narrowly scoped tokens reduce the value of stolen credentials.
Privileged-access controls and regular access reviews can further reduce the damage when infrastructure is compromised. Hassium’s PAM services and IAM managed services address controls for privileged accounts and access across cloud and hybrid environments.
Could a breach expose your entire infrastructure?
Frequently Asked Questions (FAQs)
Was every FirstVDS customer affected?
No. FirstVDS said only part of its infrastructure was affected. Follow the provider’s notice.
Why did servers keep working?
The collector mounted disks read-only from the infrastructure layer, so it did not need to run inside the guest system.
Has the VMmanager 6 vulnerability been fixed?
On 21 October, FirstVDS said the vendor reported the flaw closed, but kept the panel isolated while affected nodes were cleaned and verified. The FirstVDS cyberattack demonstrates that a virtual server’s security also depends on the management plane.
The FirstVDS data breach shows why this layer matters: if it can access tenant disks, compromise can expose stored passwords and keys even when the VM looks healthy.
