2023 · O - Public administration and defence · Cyberespionage intrusion with data exfiltration
Analysed 2026-11-06 by Hermes
Open this case in the tool →Cyberespionage intrusion with data exfiltration
No DV evidenced
Alternative: Expertise to Execution
(1) No doctrinal expectation at the victims can be established: the targets are an unnamed, diffuse set of diplomatic entities in South America (EuRepoC receiver category State institutions / political system, subcategory embassies), and no victim organisation, policy, statement or national advisory was identified in any source. (2) What the record shows is attacker-side only: Microsoft reported on 13-02-2023 that DEV-0147 was compromising diplomatic targets in South America, using ShadowPad for persistence and QuasarLoader to deploy further payloads, with post-exploitation activity including the 'abuse of on-premises identity infrastructure for recon and lateral movement' and Cobalt Strike for command-and-control and data exfiltration; the initial access method was not disclosed, and phishing or unpatched applications are only 'likely vectors' per reporting. EuRepoC scores the impact as minor data exfiltration with no disruption. (3) The entry vector is unknown and not load-bearing, and no other lifecycle stage yields a victim-side mechanism: detection and dwell time are undocumented (Microsoft's own tooling detected the activity; nothing states when or how the victims noticed), containment, egress protection, recovery and the victims' response and disclosure are all absent from the record - the incident was disclosed by an IT-security company, not by the victims. Reading the lateral movement and undetected exfiltration back into victim-side directory-hardening or egress-monitoring gaps would be the rejected attacker-technique-therefore-DV-Type inference: almost any successful intrusion can be postulated to imply some victim gap, but no source states one. Under the decision rule, the reporting confirms impact only, so the case is Unknown; this is a finding about the transparency of state-espionage reporting, not a coding gap.
EuRepoC row; the case file is internally consistent (name, description and receiver category all describe the same DEV-0147 campaign). Victim is a diffuse, unnamed population of diplomatic entities across several South American countries, so Country is null: the dataset's receiver_country 'South America' is a region, not a country, and no individual victim was named in any source. Sector recorded as public administration (all reported victims are diplomatic missions); the method spec would leave sector blank for a diffuse campaign, but the output check requires one exact CBS SBI entry. Year 2023 is the disclosure year (Microsoft thread dated 13-02-2023, attribution_date in the case file); no separate incident start date is recorded. The primary source (the Microsoft Security Intelligence thread on X, https://twitter.com/MsftSecIntel/status/1625181255754039318) could not be opened directly from this environment, so its statements are cited as reported by the three opened articles and it is not cited as a URL; no Microsoft blog post, victim statement, CERT advisory or regulator document on this campaign was found, and follow-up searches (2023-2024) produced no incident-specific elaboration - every report traces back to the same thread. Searches for lifecycle detail (detection, dwell time, victim response, recovery) came up empty; Unknown rests on an exhausted search space, not a skipped search. No status command was given for this run, so no progress reports were written.