Recovering Losses from Hosting Providers After Cyberattacks: Legal Steps for Russian Businesses
Russian entrepreneurs do not need to follow news reports to learn about cyberattacks targeting hosting providers. When a business website stops working, partner and competitor sites become unreachable, backup copies cannot be downloaded, virtual server images disappear, network settings are lost, or cloud service contents are affected, the cause is often a cyberattack on the hosting provider.
Businesses must then spend time, effort, and money restoring information, wait for an official statement from the hoster, and attempt to recover losses using the algorithm described below. The terms hosting provider and hoster are used interchangeably.
Can Losses Be Recovered from a Hosting Provider?
Businesses have the right to claim damages from a hoster under Articles 15 and 393 of the Russian Civil Code, although guarantees of compensation are absent. Prospects for recovery depend on contract conditions, provider obligations, incident details, and correct documentation proving that losses were actually incurred.
Actions for Affected Businesses
1. Document the consequences of the cyberattack by collecting evidence of disrupted company resources and resulting harm. Preserve official notifications from the hosting provider about the attack and restoration progress, error messages and support correspondence, records of page unavailability, data from technical logs and availability monitoring, proof of information loss or damage, and evidence of interrupted business processes. Specialized evidence-fixation services or a notary can be used to preserve webpage content, notifications, and email exchanges. Notarial protocols are not mandatory but significantly strengthen proof, especially if data later changes or disappears.
2. Calculate and document losses, separating real damages from lost profits. Real damages include costs to restore the website and emergency infrastructure migration, all supported by contracts, invoices, acts, and payment documents. Lost profits cover income missed due to inability to accept orders while the site is down; proving this requires evidence of realistic revenue potential after necessary expenses.
3. Review the contract with the hosting provider. Services are often provided under a public offer accepted during registration or payment. Clients should retain the applicable version and examine tariff conditions, service-level agreements, and related documents. If the contract states that clients must create backups themselves, recovering losses for data loss becomes difficult. Provisions may release the hoster from liability for cyberattacks, DDoS attacks, or third-party actions, yet such clauses do not automatically exempt the provider. Courts distinguish between force-majeure circumstances and independent contractual exclusions, evaluating whether the attack could have been prevented and its link to specific obligation breaches. Contractual limits on liability cannot shield grossly unprofessional conduct that undermines the core obligation.
4. Submit a claim to the hosting provider. The written claim must reference the contract and services used, describe the incident and consequences, identify violated obligations, provide a loss calculation, attach supporting documents, and demand compensation plus possible recalculation of service fees. Claims follow the procedure specified in the contract, usually by mail or electronic means, with proof of sending and content preserved. Missing contractual deadlines does not remove the right to sue for damages but may affect additional compensation.
5. Evaluate court prospects if compensation is refused. Businesses may file in arbitration court after completing pre-trial procedures. Success requires proving contractual obligations, their breach, the existence and amount of losses, and causation. The provider bears the burden of proving any exempting circumstances.
Court practice indicates that a cyberattack is neither an unconditional ground for releasing the hoster from liability nor a sufficient basis for automatic recovery. The primary task for affected businesses is to gather and preserve evidence of impact on operations, confirm incurred losses, review contract terms, and follow the required claims procedure. Companies that have not yet faced such incidents should locate and save their contract or offer text for quick reference during emergencies.
Related articles
Webiomed AI Platform Processes Millions of Medical Records Daily on Certified RED OS Infrastructure
The Russian Webiomed platform now serves more than 4,000 medical organizations across 55 regions and supports over 300,000 physicians. Its algorithms analyze up to one million electronic health records every day, generating recommendations that physicians must review and approve. The entire server infrastructure runs on RED OS, which holds FSTEC Russia certification for use in critical information infrastructure. Legal responsibility for any harm remains with the medical organization and, in some cases, the individual physician, even when AI suggestions are involved. The article highlights risks such as incomplete data, synchronization errors that could revoke physician access via RED ADM directory services, and the need for selective recovery tools like Granulex Recovery. Joint testing by MDIS and RED SOFT confirmed that Granulex Recovery can restore specific objects and attributes without stopping the directory service. Questions remain about where liability falls when errors occur at the intersection of the algorithm, medical systems, and underlying IT infrastructure.
Russian Ombudsman Proposes Eurasian Code of Ethics to Regulate Destructive Online Content
Russian human rights commissioner Yana Lantratova has urged the Eurasian Alliance of Ombudsmen to develop a shared code of ethics for handling destructive digital content that targets children and adolescents. The proposal, presented on 16 November at the alliance's eleventh meeting in Moscow, addresses the absence of a formal definition of destructive content in Russian law, which currently hinders effective blocking of harmful materials. Lantratova highlighted seven key categories of destructive content, including normalization of violence, incitement to suicide, cyberbullying, fraud, and recruitment into terrorist or extremist groups. She cited a sharp rise in terrorism-related criminal cases involving minors, from 86 in 2024 to 239 in 2025 according to the Investigative Committee. The ombudsman also warned about the growing use of deepfakes for child extortion and advocated a platform-engagement model over outright bans, which she said risk increasing curiosity among young users. Representatives from Bahrain, Iran, Kazakhstan, Kyrgyzstan, Mongolia, Tajikistan, Uzbekistan, Sri Lanka, Serbia, and Armenia participated in the discussions.
Unconfirmed Reports of Steam Blockade in Russia: Valve Faces User Data Demands and Tax Scrutiny
On November 16, media outlets and Telegram channels reported that Russian authorities are demanding user data from Valve's Steam platform, including accounts registered in Kazakhstan, while threatening to block the service. The claims also suggested plans to track undeclared income from high-value in-game skins, but no official statements or documents have confirmed these assertions. The original source was an analytical piece by ProFinance that cited unnamed sources without specifying any government agency, official, or legal document. Roskomnadzor, the Federal Tax Service, and other agencies have made no such announcements, and Valve has not confirmed receiving any requests. Confirmed information is limited to tax payments: Kazakhstan's Committee of State Revenues reported that Valve paid approximately 2 billion rubles in VAT for the first half of 2026, the highest among foreign internet companies. This amount more than doubled compared to the same period in 2025, attributed to Russian users relocating their accounts to the Kazakh region after Visa and Mastercard exited Russia. Vice Speaker of the State Duma Vladislav Davankov opposed any potential blockade, comparing it to freezing bank deposits, and pledged to raise the issue at the Duma session on November 17.
Russia's MinTsifry Mandates Qualified Electronic Signatures for Remote eSIM Registration to Combat Fraud
Russia's Ministry of Digital Development has directed telecom operators to allow remote eSIM issuance and contract signing exclusively through enhanced qualified electronic signatures (UKEP). The use of enhanced unqualified electronic signatures (UNEP) via the GosKlyuch system will be prohibited starting December 1. Operators must re-integrate with GosKlyuch exclusively through the SMEV interagency system and verify all remotely issued eSIMs registered before November 15. The measures address widespread fraud involving unauthorized number porting to attacker-controlled eSIMs, enabling interception of SMS codes for banking and messenger access. Independent experts note that UNEP certificates require only a verified Gosuslugi account, making them vulnerable to account takeover, while UKEP demands stricter identity verification. Over 15.7 million UNEP certificates were issued through GosKlyuch in the first eight months of 2026.