2022 · Russia · C - Manufacturing · Hack-and-leak data theft with document publication
Analysed 2026-11-06 by Hermes
Open this case in the tool →Hack-and-leak data theft with document publication
No DV evidenced
Alternative: none defensible
(1) The victim is the Kalashnikov Concern, the Rostec-controlled Russian manufacturer of small arms, guided munitions and drones, whose crown jewels - weapons design documentation - would be expected to be protected differently from commodity records given its defence-industry role. (2) The only account of the incident comes from cybersecurity writer Jeffrey Carr, who states he worked directly with the GURMO offensive cyber operators said to have run the hack-and-leak: servers hacked, more than three terabytes downloaded spanning technical specifications of civilian and military weapons and the company's financial data, and the dump shared with US and UK intelligence services (Carr's Inside Cyber Warfare newsletter, 15 March 2022; Cybernews interview, 16 March 2022). Neither Kalashnikov, nor Rostec, nor any Russian authority acknowledged an intrusion; there is no CERT, regulator or forensic report; and secondary reporting carries Carr's claims without independent verification - SC Media describes GURMO as having leaked documents it claimed it stole, and the ETH Zurich researcher Stefan Soesanto notes that between the start of the invasion in February 2022 and November 2023 no credible reports existed on GURMO's activities in cyberspace. (3) The reporting therefore confirms claimed impact - exfiltration and leaking, both asserted by the attacker's side - and no lifecycle stage (entry, containment, detection/dwell, egress monitoring, recovery, response) documents a victim-side condition: no gap's origin or break is evidenced anywhere, the entry vector is unknown and not load-bearing, and inferring a data-governance or egress gap from what the attacker says it took is impact-only reasoning the method rejects (the exclusions of RM16 and RM35 forbid coding impact alone). The one victim-side detail in the record - that the breach happened, per Carr, in the words of the newsletter, 'just three months after the company replaced its Director of Cybersecurity' - is ambiguous (Carr himself reads it as possible awareness of vulnerability and an attempt to improve) and cannot carry a classification. This is an openly claimed state hack-and-leak signalling operation in wartime, atypical for the framework: the leak itself is the operation's goal, the victim's silence fits the 'nothing happened' communications posture Carr describes for Russia, and the victim-side decision loop is structurally unobservable. DV-Type Unknown, insufficient evidence, no assessable mechanism.
One-sided sourcing: the row itself notes the incident was reported exclusively via Jeffrey Carr's newsletter; Carr states he worked with two GURMO offensive cyber operators and received the documents directly from them, and EuRepoC codes attribution as attacker-confirms via anonymous media statements. No victim confirmation: searches in English and Russian (incl. TASS, Rostec, kalashnikovgroup.ru) found no acknowledgment by Kalashnikov or any Russian authority. The case file's source_url (jeffreycarr.substack.com) redirects to the same article at insidecyberwarfare.com; that final URL was opened and is cited. Victim-side lifecycle (entry, detection, dwell, response) is undocumented; victim silence matches the Ihtamnet-style 'nothing happened' posture Carr describes (O'Reilly article, 22 March 2022). Soesanto (RealClearDefense, 2024) finds no credible reporting on GURMO cyber activity existed from Feb 2022 to Nov 2023 and that outlets repackaged GURMO claims without due diligence. Other incident at the same victim, not this row: in September 2023 GURMO reportedly disabled 700+ switches and 13 servers at K-Korp, the network operator serving the Kalashnikov Concern (https://gordonua.com/news/war/millionnyj-ushcherb-kiberspetsialisty-hur-atakovali-rostelekom-i-lukojl-smi-1755537.html, citing Babel). Sector: the dataset codes the receiver as Critical infrastructure / Defence industry; coded C Manufacturing because weapons manufacture is SBI section C and Kalashnikov is a company, not a government or military body. Per security policy no leaked files or leak-site content were opened; the analysis rests only on published reporting. Unattended run: nothing was encountered that requires consent.