← Breach analysis by the Dual Vulnerabilities framework

Albatros drone maker data leak (Cyber Resistance, 2024)

2024 · Russia · C - Manufacturing · Data theft and leak via hack of CEO personal data (hack-and-leak)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft and leak via hack of CEO personal data (hack-and-leak)

Dual vulnerability type

Strategy to Execution

Evidence coverage: 2/6 stages, weight 7/60

Decisive stage: egress (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) Albatros LLC, a US-sanctioned Russian drone manufacturer resident in the Alabuga special economic zone, held itself to a formal secrecy regime: the business plan it submitted to the SEZ management (as analysed by InformNapalm from the leaked files) names CEO Alexey Florov as responsible for documentation and secrecy. (2) In practice, the Cyber Resistance hacktivists claim to have taken more than 100 GB of internal company data, much of it classified - technical documentation, UAV drawings, sanctions-evasion material and correspondence - by accessing Florov's personal data, and the incident surfaced only through the attackers' own April 2024 disclosure; Albatros never publicly acknowledged it. The entry technique is undisclosed and is not load-bearing. (3) This is a doctrinal-material gap rather than mere weak security: the classification/secrecy requirement existed as a formal artefact (doctrinal origin) but was not realised in operational reality - the crown jewels sat reachable through a personal account outside governed systems and left in bulk without anyone at the victim noticing (execution break). The classification rests on the egress stage, the only stage whose condition a source actually documents; the detection gap (never detected by the victim) points secondarily to Expertise to Execution but rests on inference and cannot win the tie-break. All of this evidence originates with the attackers and their InformNapalm partner and is not independently verified, which caps confidence. RM16 (Strategy to Execution lens): the company's classification and secrecy requirements were never implemented in systems and processes - the leak shows classified internal documents and drawings exposed far beyond what the governed handling of them should have allowed, sitting where the CEO's compromised personal data reached them (causal role: Amplifying). RM34 (Strategy to Execution lens): monitoring and alert-handling that should cover executive accounts and bulk transfers was not implemented or operated as intended - neither the intrusion into Florov's personal data nor the 100 GB exfiltration was noticed by the victim, only published by the attacker on 15 April 2024, two weeks after a Ukrainian drone strike on the Alabuga site (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

All incident evidence originates with the attacking group (self-attribution on its Telegram channel) and the InformNapalm analyses of the leaked files; provenance and veracity are not independently verified (the case file's own description says so) - the substantive claims are therefore scored as attacker-claim-grade (speculation). The attackers' Telegram channel (t.me/cyberResistanceUA/397, the dataset's attribution_source_url) was deliberately not opened per the research boundaries (attacker channel); the same claim is cited as reported by The Record. Victim statement: none found - Albatros, the Alabuga SEZ and Russian authorities issued no public acknowledgement of the hack in the reporting reviewed. The victim column's 'Chief Executive Office' is a typo for Chief Executive Officer (data quality). No earlier Albatros incident was found in the dataset or reporting, so no recurrence marker was coded. Link check: informnapalm.org blocks automated access (HTTP 403); the page was opened and read during research.