2022 · Russia · O - Public administration and defence · Data theft and doxing (hack-and-leak email dumps)
Analysed 2026-11-07 by Hermes
Open this case in the tool →Data theft and doxing (hack-and-leak email dumps)
No DV evidenced
Alternative: none defensible
(1) No doctrinal expectation at any of the victims can be established: no security policy, programme, standard or public statement of Tendertech, Synesis or GUOV i GS (or the unnamed first receiver) appears anywhere in the searched record. (2) What happened operationally is known only from the attackers: in the DDoSecrets release of 19 April 2022, Anonymous claimed to have stolen 426,000 emails (160 GB) from Tendertech, 15,600 emails (9.5 GB) from GUOV i GS (Ministry-of-Defense-owned construction company; claimed mailbox range 25 October 2021 to 13 April 2022) and data on the Synesis/Kipod surveillance system (per the hackers and DDoSecrets, gathered in August 2020 and published in response to the Belarusian government taking control of the system). None of the victims acknowledged an intrusion; no entry vector was ever reported; no regulator, court or victim investigation of these four companies appears in the searched sources, including Russian-language searches. (3) Because the reporting confirms impact only (publication of the data), no victim-side failure point can be placed on either DV axis: every candidate gap - undetected mailbox exfiltration, late awareness, non-disclosure before the attacker's leak - would be inferred from the attackers' own claims rather than documented, and an inference from an unverified claim is exactly what the exclusions for the egress and disclosure markers forbid. The campaign record is itself documented as partly unreliable: the datasets come from anonymous submitters, DDoSecrets attaches a cyberwar disclaimer warning of altered or implanted data or false personas, and some high-profile Anonymous claims from this period were later shown false or insignificant. The classification therefore rests on all six stages being undocumented on the victim side - entry, containment, detection, egress, recovery and response - and the decision rule for reporting that confirms impact only applies: DV-Type Unknown, atypical case flagged in Notes. No entry vector, no victim-side mechanism, and therefore no load-bearing stage exists.
One row aggregates four receivers (the first is 'Not available'); the dataset description additionally names Neocom Geoservice, which is not in the receiver_name list - all were part of the same 19 April 2022 DDoSecrets batch. The dataset's cybernews source_url (8 April 2022) describes a different, earlier batch (Petrovsky Fort, Aerogas, Forest), not this row's victims; the April 20 securityaffairs report is the article that covers this batch. Every incident detail (intrusion, volumes, date ranges) rests on Anonymous's self-attributed claims published via DDoSecrets and relayed by press; no victim statement, regulator notice or Russian-media coverage of these four companies was found (Russian-language searches run). DDoSecrets attaches a standard cyberwar-category disclaimer about possible malware, altered or implanted data and false flags/fake personas to these datasets (as reported by The Intercept). Synesis/Kipod: the published data is said to have been gathered in August 2020; Synesis is a surveillance-software company of Russian/Belarusian domicile operating the Kipod platform largely in Belarus - the dataset codes receiver_country Russia for all four positions, which is why Country is Russia. Sector reflects the coded critical victim of the batch (GUOV i GS is receiver_category 'Critical infrastructure / Defence industry' and wholly owned by the Russian Ministry of Defense per Security Affairs); the other named victims would fall under K (Tendertech, financial-document processing) and J (Synesis, software). Unnamed first receiver is kept in the Victim string exactly as the case file writes it. Atypical case for the framework: a hacktivist hack-and-leak batch in the 2022 cyberwar wave, disclosed only by the attacker (dataset field source_disclosure: 'Incident disclosed by attacker'); no victim-side lifecycle evidence exists at any stage.