← Breach analysis by the Dual Vulnerabilities framework

Russian defence-sector organisations espionage (Librarian Ghoul, 2024)

2024 · Russia · O - Public administration and defence · Cyber-espionage data theft via targeted phishing

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Cyber-espionage data theft via targeted phishing

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) No doctrinal expectation can be identified at the victim side: the row describes an espionage campaign against an unnamed population of Russian design- and engineering-intensive organisations - research institutes, aerospace and aviation companies, and manufacturers of equipment for the gas-processing, petrochemical, nuclear-power and defence industries (Kaspersky, 5 September 2024) - and no victim organisation is named anywhere in the reporting. (2) What the sources document is the attacker's method and the campaign's reach, nothing of the victims' own situation: Kaspersky's July 2024 report describes targeted e-mails delivering a .SCR installer disguised as an official document, which archives Office documents and Telegram Desktop data, harvests browser-stored credentials with a password-recovery utility, installs legitimate user-monitoring software and e-mails the collected archives to attacker-controlled addresses; the September 2024 follow-up names the group Librarian Ghouls and records added collection of CAD files (SolidWorks .SLDPRT, KOMPAS-3D .cdw, .dwg, .m3d) and PDFs. The campaign was surfaced by Kaspersky's own telemetry, not by any victim report, and Kaspersky explicitly does not attribute it. (3) Because no source documents any targeted organisation's policy, resourcing, monitoring, detection timing, dwell time or response, no lifecycle stage yields origin-and-break answers grounded in evidence; the documented entry mechanism (users running a disguised .SCR attachment) describes the attacker's move, and reasoning from it to a victim gap is the rejected pattern - Kaspersky's generic recommendations (mail-gateway protection, endpoint protection, awareness training) are advice to the sector, not evidence that a given victim lacked them. The reporting confirms method and impact only (EuRepoC codes the incident as hijacking not used, minor data exfiltration, no disruption), so the decision rule sets the DV-Type to Unknown for insufficient evidence. The entry vector is documented but is not load-bearing for a DV classification, because the control state of no victim organisation is known.

Sources

Notes

Diffuse multi-organisation campaign row: the dataset carries no receiver_name and no named victim, so the victim is named descriptively and 'victim established' is false. Single-source evidence base: all lifecycle information comes from Kaspersky vendor telemetry (July and September 2024 reports); no victim statement, regulator or CERT document exists for this incident, and attribution is explicitly open (initiator_country Unknown). Sector is coded O Public administration and defence because the dataset's leading receiver_subcategory is Defence industry and the row name frames the case that way; in reality the targeted population spans several sections (research institutes, manufacturing, transport). The June 2025 Kaspersky press release documents a later campaign wave (from December 2024: night-time remote access, credential theft, crypto-miner deployment, hundreds of corporate users in Russia plus Belarus and Kazakhstan); that wave is follow-up activity and not the 2024 espionage incident the row describes, so it is not used for classification. No related_rows in the case file and no earlier result for this victim in the output directory. Security policy: research used only vendor reports and press; no leak sites, dumps or actor contact were used, and nothing requiring consent was encountered.