2022 · O - Public administration and defence · Cyber-espionage intrusion campaign with custom backdoor, no recorded disruption or confirmed data loss
Analysed 2026-11-06 by Hermes
Open this case in the tool →Cyber-espionage intrusion campaign with custom backdoor, no recorded disruption or confirmed data loss
No DV evidenced
Alternative: none defensible
(1) There is no retrievable doctrinal expectation at the victim: the row and every source opened describe a diffuse campaign against unnamed organisations, and Symantec - the sole primary source and the attributing party recorded in the case file - declined to name the victims or the countries targeted (The Record; Symantec blog). (2) What the record documents is the attacker's side: Lancefly used the custom Merdoor backdoor, which has existed since at least 2018, with an updated ZXShell rootkit, PlugX and ShadowPad, in highly targeted espionage intrusions on government, aviation, education and telecoms organisations in South and Southeast Asia from mid-2022 into Q1 2023, the tool's deliberate low prevalence read by Symantec as a desire to stay under the radar; the case file records no disruption, no confirmed data breach or exfiltration, and economic impact none. (3) The DV framework measures where a specific victim's own strategy or expertise failed to reach execution or leadership; here the primary source itself states the initial infection vector is not confirmed (evidence for phishing, SSH brute forcing and public-facing server exploitation 'is not definitive' - Symantec blog; BleepingComputer), the campaign was uncovered by an external vendor rather than by any documented victim-side detection, and no source makes any victim's doctrine, expert reporting, resourcing or disclosure visible, so no lifecycle stage yields a victim-side mechanism with evidenced origin and break. Per the decision rule (reporting confirms impact only; primary source states cause undetermined; diffuse multi-organisation campaign with no victim organisation in the framework's sense), DV-Type is Unknown and no confidence score is issued. The suspected entry methods are attacker-side TTP patterns and are not load-bearing for any DV-Type. No risk marker is coded: the record supports no concrete victim-side condition traceable to evidence for a named organisation (RM22, RM27, RM28 and RM34 each fail their evidence or exclusion requirements here), and the method spec forbids stretching markers to fill the gap.
Atypical, diffuse case: a state-linked espionage campaign spanning two regions (South and Southeast Asia) and four sectors with no victim organisation named in the dataset or in any source opened; Symantec explicitly declined to name the victims or countries (The Record). Under the method spec, Country and Sector would be blank for an unspecified multi-organisation campaign; Country is left null (eurepoc_extra.receiver_country holds only the regions 'Southeast Asia (region)' and 'South Asia (region)' - never guessed), while the output check requires exactly one CBS SBI entry, so Sector is coded 'O Public administration and defence' from the case file's dominant receiver category (State institutions / political system; Government / ministries). Year 2022 from eurepoc_extra.start_date (01.01.2022); the described campaign began mid-2022, while Symantec dates the Merdoor backdoor to 2018 with earlier campaigns in 2020-2021 in the same geographies. Victim is not established as an identifiable organisation, which independently caps confidence; DV-Type Unknown with no assessable victim-side mechanism means no score is issued at all. Attribution: Symantec states none of the overlaps (ZXShell certificate 'Wemade Entertainment Co. Ltd' linked to APT41, formdll.dll linked to APT27/Iron Tiger, PlugX and ShadowPad use) are strong enough to attribute Lancefly to a known group; 'suspected China-linked' reflects those tool overlaps as reported, not a confirmed attribution. Initial infection vector unconfirmed by the primary source; the dataset's mitre_initial_access 'Exploit Public-Facing Application' is one of several suspected vectors and is not an incident-confirmed fact. No related_rows in the case file. Unattended run: no consent-gated actions were required.