"Unfortunately, it is impossible to recover all data," Beget said about VPS data.
How the intrusion unfolded on the night of November 1st
Beget says the incident began on the night of November 1st, when an attacker gained access to the management systems for the company's entire architecture and deployed malware that erased server data. The provider detected the attack shortly after the destructive code activated and disconnected all servers from the network to prevent the activity from spreading across its infrastructure.
Scope of the destruction: VPS, S3, Kubernetes, CDN and IP settings
The company reported that "all data in its cloud infrastructure" was lost, explicitly naming virtual private servers (VPS), S3 storage, and Kubernetes clusters. Configuration items were also affected: CDN settings and IP configurations were erased. Beget said VPS binary backups were completely lost; VPS file backups survived only in part. A November 6 assessment narrowed that further, saying backups would be available for roughly half of VPS users.
Beget added that its investigation did not find evidence the attacker attempted to download or modify data on the compromised servers, and that the incident appears to have been focused solely on destruction.

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleRestoration progress and technical constraints
More than a week after the incident, Beget reported partial restoration: about 60% of its shared hosting and 40% of the dedicated servers it manages had been brought back online, and recovery remained in progress. The company cautioned that even when backups exist, identifying and matching each backup to the correct customer account is "technically complex" and will take time.
The scale of the recovery is large: roughly 1,000 servers need manual inspection for vulnerabilities and hidden scripts before they can be returned to service, the firm said. That manual vetting is part of Beget's decision to treat every part of its infrastructure as potentially infected and to "clean out everything we can and rework every potentially vulnerable point, including those that previously did not appear to pose a risk."
Operational and legal response: police, government agencies, and outside firms
Beget notified police and government agencies and is working with cybersecurity firms to remediate the incident and accelerate recovery. The company has emphasized a cautious posture: isolating infrastructure early, rebuilding components from scratch where necessary, and engaging external specialists to support the investigation and restoration effort.
What this means for online stores, media outlets, and educational services
- Online stores — Many of Beget's customers are e-commerce sites. For merchants hosted on affected systems, the combination of erased VPS data and lost CDN or IP configurations can cause extended downtime, inventory and order-data gaps where backups are unavailable, and delay in buyers' access while DNS and delivery settings are reconstructed.
- Media outlets — Media customers that rely on CDN settings and IP maps may face interrupted content delivery and longer recovery times if those configurations cannot be restored quickly from backups.
- Educational services — Education providers hosted on Beget's platform may lose course materials or user data where file backups are not available; Beget's assessment that file backups will be available for only about half of VPS users signals that some course content and student data could be permanently lost for affected customers.
Beget serves more than 200,000 customers, including online stores, media, and educational services. The company's account of the attack frames this as a destructive, management-layer compromise that forced a rebuild of core services and a painstaking, manual recovery process. The immediate facts are stark: data-zeroing scripts erased key storage and configuration layers, many backups were destroyed, and restoring full service requires both technical matching of surviving backups to accounts and manual sanitization of roughly 1,000 servers.
The company says recovery is ongoing and that some data cannot be recovered; authorities and cybersecurity firms are now part of the remediation effort. Observers will be watching how long the manual inspections and reconfiguration tasks take, and whether the surviving backups can be mapped accurately to affected customers.
Source: BleepingComputer — Russian cloud firm Beget rebuilds from scratch after data wiper attack




