← Breach analysis by the Dual Vulnerabilities framework

Unspecified organisation FakePenny ransomware attack (Moonstone Sleet, 2024)

2024 · M - Professional, scientific and technical activities · Ransomware attack after a months-long undetected intrusion

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Ransomware attack after a months-long undetected intrusion

Dual vulnerability type

Expertise to Execution

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

Decisive stage: detection (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) The victim is a single company in the defence industrial base - unnamed in the dataset and identified in the reporting only as an unnamed defense technology company - where the standing expectation is material: known, standard detection and egress monitoring means exist for publicly documented North Korean intrusion tradecraft, and Microsoft had published Defender signatures and behaviour detections for this actor's toolset (SplitLoader, YouieLoad, credential-theft tools). (2) In practice the actor compromised the company in February 2024, ran network, user and credential theft activity inside the network without the company noticing, stole credentials and intellectual property, and two months later, in April 2024, deployed the custom FakePenny ransomware with a $6.6M BTC demand; the activity was surfaced by Microsoft's tracking of the actor, not by the company's own monitoring, and the encryption caused disruption beyond 24 hours with days of functional impact. (3) That is a gap within the material column: the technical remedies were known and applicable, yet did not work in operations for roughly two months; no source documents a strategic artefact, programme or budget decision that failed to translate (which would point Strategy to Execution or Strategy to Leadership) or an expert warning leadership ignored (Expertise to Leadership), so the classification rests on the detection stage and its execution break, with the entry vector undisclosed and not load-bearing. RM34 (Expertise to Execution lens): available tools were insufficiently configured, staffed, tuned or maintained to detect the activity - a two-month dwell (February to April 2024) ended only when Microsoft's external tracking surfaced the ransomware deployment (causal role: Obscuring). RM35 (Expertise to Execution lens): the egress monitoring a defence-sector company could implement and tune did not interrupt or reveal the outbound theft of credentials and intellectual property during the undetected dwell (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Victim is unnamed: Microsoft withholds the company's identity and country, so Country is null (the case file also carries receiver_category Unknown). Secondary reporting reporting Microsoft's analysis describes the ransomware victim as an unnamed defense technology company (Decipher via malware.news, The Register, 28-29 May 2024); HelpNetSecurity lists drone-technology and aircraft-parts companies among the actor's other targets, so the Sector entry (M Professional, scientific and technical activities) is a proxy for the reported defense-technology description and the case file's own category is Unknown. The Register dates the initial compromise to December 2023 while Microsoft's blog and the Decipher article give February 2024 (two months before the April deployment); the primary timeline was followed. EuRepoC's intelligence_impact says no data breach/exfiltration, which conflicts with the Decipher article's account that the initial February intrusion first stole credentials and intellectual property - the egress stage is scored as inference and contributing for that reason. The fourth source_url in the case file (a BleepingComputer article on Scattered Spider and Qilin ransomware) describes a different incident and is not cited; it appears to be a sidebar link picked up when the dataset scraped the FakePenny article. No consent-gated actions were needed in this run.