← Breach analysis by the Dual Vulnerabilities framework

Skolkovo Foundation data theft (sudo rm -RF, 2023)

2023 · Russia · M - Professional, scientific and technical activities · Data theft via partial network intrusion

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft via partial network intrusion

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) The Skolkovo Foundation is the Russian state-linked development institution running the Skolkovo innovation hub; it operates its own IT estate on physical capacity (website sk.ru, e-mail, financial and analytical systems, the resident portal, an internal file-exchange platform), and it was sanctioned by the United States over its ties to Russia's defence sector, so protecting project documents and partner data is a core expectation of the organisation. (2) In the night of 28-29 May 2023 Ukrainian hacktivists gained partial access to a number of information systems and network resources, in particular the file-exchange platform on the Foundation's own physical servers; presentations, photos, contracts, partner and counterparty lists, CRM contact bases and some personal ecosystem documents were taken, internal screenshots (reportedly including GitLab and Confluence resources) were posted, and public web resources were suspended; the victim restored the main functionality within about a day and announced full restoration of the core systems on 31 May 2023, with a law-enforcement investigation opened. (3) The DV framework requires a victim-side mechanism - an expectation or known remedy, and where the chain broke - at some lifecycle stage. No source supplies one: neither the victim's own statements nor Russian or English reporting ever said how the intrusion into the file-exchange server was possible, reporting states outright that the breach method was still unclear (CyberSecurity SEE), and no outcome of the law-enforcement investigation has been published. Nothing documents a missed known remedy, an ignored warning, a policy not implemented or a decision deferred at entry, containment, detection, egress, recovery or response, so no origin-and-break pair can be evidenced and no DV-Type can be assigned; the entry vector is unknown and not load-bearing. The response stage in fact went well (acknowledged within a day, disclosed the same day on its own channel, recovered in about two days), but that is absence of bad news, not positive evidence that doctrine and execution were aligned, so 'No DV evidenced' is not supported either. The attackers' claims that the infrastructure was destroyed and that they hold all documents and project source codes are unverified and cannot found a DV-Type. The case is a symbolic hacktivist strike in the Russia-Ukraine cyber conflict (The Record reads it as symbolic rather than practical impact); under the decision rule the classification is Unknown: the reporting confirms impact only and leaves the cause undetermined.

Sources

Notes

eurepoc row; victim, country (Russia) and year (2023, start date 28.05.2023) taken from the case file and confirmed in the sources opened. Actor naming is ambiguous in the record itself: the case file's description notes that Skolkovo's 29 May Telegram post named the Ukrainian CyberFront as claiming responsibility, while the central claim post came from the channel sudo rm -RF - kept both in Actor. The attackers' Telegram channel was not opened directly (security policy limits attacker channels to what legitimate press reports); their claims are cited as reported by The Record and Habr and are unverified - The Record's account, citing a Russian Telegram leak-analysis group, says no critical user data was compromised, and the victim's own post reports only partial access. Habr reports stolen material included CRM contact bases and some personal documents of ecosystem participants. No regulator or formal investigation of the victim's controls was found; the law-enforcement investigation mentioned by the victim produced no published findings. rbc.ru returned HTTP 401 to automated access during research; its content is covered here through the victim's Telegram post, TASS and Habr reporting, so it is not cited. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research. Unattended run: no consent-requiring actions were needed.