2020 · Taiwan · K - Financial and insurance activities · Cyber-espionage intrusion with credential dumping and data theft
Analysed 2026-11-06 by Hermes
Open this case in the tool →Cyber-espionage intrusion with credential dumping and data theft
Expertise to Execution
Evidence coverage: 3/6 stages, weight 19/60
Decisive stage: containment (clearest evidence) · Alternative: Strategy to Execution
(1) The victims - at least two financial organizations and one manufacturing company in Taiwan - were holding exactly the material state-linked espionage wants (business contacts, investments, smart card reader and account data), and the baseline expectation for supervised financial institutions is that known vulnerabilities get patched, credential-theft tradecraft gets flagged, and outbound transfers are watched. (2) In practice, from December 2020 Antlion operated inside these networks for close to 250 days (financial organization) and around 175 days (manufacturing company): it deployed the custom xPack backdoor, saved the SAM/SYSTEM/SECURITY registry hives and dumped LSASS on several machines within the organizations, executed code remotely via PsExec and scheduled tasks, leveraged EternalBlue inside the backdoor and CVE-2019-1458 for privilege escalation, and staged and exfiltrated password-protected WinRAR archives - all discovered only by Symantec's research, not by the victims. (3) The classification rests on the containment stage, the best-documented gap (Symantec's primary forensic account): every remedy needed was known and available expertise - the exploited vulnerabilities had been patched since 2017 and October 2019 (the case file records zero_days 'No'), and detecting hive saves, LSASS dumps and PsExec lateral movement is standard operations practice - yet none of it was realised in the victims' operations for months; the origin is material and the break is execution, which is Expertise to Execution. No source documents a victim policy, standard or leadership decision, so the doctrinal column is not evidenced (no Strategy to Execution or Strategy to Leadership), and no ignored expert warning is documented. The entry vector is unknown (Symantec cannot state it with certainty) and explicitly not load-bearing; the detection gap (250-day dwell, external discovery) and the egress gap (undetected staging and exfiltration) point to the same type. (4) RM41 (Expertise to Execution lens): the privilege and directory hygiene that specialists are expected to keep clean - admin credential reuse, service tiering, ticket hygiene - was not cleaned up: the attackers dumped credentials from several machines over months, escalated with CVE-2019-1458 and carried a Mimikatz-based golden ticket tool, so lateral movement went unimpeded (causal role: Amplifying). RM18 (Expertise to Execution lens): the exploited vulnerabilities were known and remediable long before the intrusion (EternalBlue patched May 2017, CVE-2019-1458 patched October 2019), but internal patching execution lagged disclosure by years, keeping them exploitable for movement (causal role: Enabling). RM34 (Expertise to Execution lens): the available detection craft for WMIC recon, ProcDump LSASS dumps and PsExec was evidently not configured, staffed or tuned to fire - close to 250 days of activity produced no internal alarm (causal role: Obscuring). RM35 (Expertise to Execution lens): egress visibility that a supervised financial institution should have had and could tune was absent in practice - staged RAR archives and BitsTransfer uploads to attacker infrastructure left the network undetected (causal role: Amplifying).
RM41 — Privilege-escalation / directory-hygiene pathRM18 — Vulnerability / patch latencyRM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapEuRepoC row carries no receiver_name: 'Antlion xPack' is the dataset's incident name (from the xPack backdoor), not an organisation - the victims are at least two financial organizations and one manufacturing company in Taiwan, all unnamed in Symantec's report, so the Victim field names them descriptively. The case file's 255-day dwell time is an approximation of Symantec's 'close to 250 days' (December 2020 - August 2021, 'almost nine months') on the financial network; the exact figure is not confirmed by any source. Symantec cannot state the initial infection vector with certainty (probable web application/service exploitation via MSSQL; malicious e-mail is a group pattern, kept as pattern-based). The egress and detection origin answers are the coder's reading of documented activity - no source states what monitoring or egress controls the victims ran. The Symantec blog URL redirects to security.com; the report was read in full at that destination. Disclosure was by the IT-security company (matches eurepoc_extra.source_disclosure); no victim statement or notification is public.