← Breach analysis by the Dual Vulnerabilities framework

UK engineering company attempted espionage spearphishing (APT40/TEMP.Periscope, 2018)

2018 · United Kingdom · M - Professional, scientific and technical activities · Attempted espionage intrusion via spearphishing and SMB credential harvesting

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Attempted espionage intrusion via spearphishing and SMB credential harvesting

Dual vulnerability type

No DV evidenced

Alternative: Expertise to Execution

Why this classification

(1) The expectation at the victim was defence against a persistent espionage actor: TEMP.Periscope/APT40 had targeted the company since at least May 2017, and in July 2018 delivered a spearphish whose design (a file:// link and a .url link opening outbound SMB sessions to attacker infrastructure, with a forked Responder NBT-NS poisoner harvesting NTLM credentials) borrowed publicly documented Dragonfly and APT28 techniques for false-flag effect. (2) What the primary forensic record shows operationally is the defence working: the attempted intrusion was noticed by the victim's own network defenders, because spelling and punctuation errors in the message alerted network defenders at the victim organization; the company analysed the lure under controlled conditions (a controlled interaction with the file share over SMB), proactively shared the attempted spearphish and its indicators with Recorded Future, and the case was disclosed by that IT-security company on 13 November 2018. Across the documented history the report speaks of attempted intrusions in May 2017 and of the July 2018 attempt; it documents no successful compromise, no data actually taken, and no disruption or recovery burden at this victim (the row's impact codings of data theft and hijacking go beyond what the underlying report supports). (3) The reviewed lifecycle therefore contains no victim-side knowing-doing or doctrinal-material gap: detection was by the victim's own staff and prompt, handling was deliberate and competent, and disclosure was self-initiated intelligence-sharing through a vendor - the positive evidence of doctrine-execution alignment that No DV evidenced requires. The entry vector is documented but not load-bearing (it was thwarted); egress and recovery are not in play (nothing was taken and nothing had to be restored); containment and response are evidenced as working; detection worked, so RM34 and RM21 stay on their exclusion clauses. (4) The two residual conditions the evidence does show are coded without a DV lens: RM24 marks the employee mailbox as the trust boundary this actor repeatedly tried to cross over fourteen months (caught each time on record, by defender scrutiny rather than by technical blocking), and RM27 marks the unhardified outbound-SMB path that made the credential-harvest design possible at all and that the report's own recommendations (restrict SMB traffic, especially external SMB authentication) target. The dataset's data-theft coding, if accepted, would instead support a secondary Expertise to Execution pattern (known remedies - patches, mail filtering - not executed), but the primary source does not state that any attempt succeeded. (5) Secondary attribution note: the group's links to FireEye/Mandiant and IntrusionTruth are attribution context, not claims the classification rests on.

Risk markers

Sources

Notes

Data-quality tension: the row codes incident_type Data theft;Hijacking with Misuse (weighted intensity 3), but the underlying Recorded Future report describes only attempted intrusions (May 2017, November 2017, July 2018) and documents no successful compromise or data loss at this victim; the classification follows the primary report. The victim is unnamed in the primary report and in follow-up press (SecurityWeek, SC Media, Security Affairs); descriptive naming used. Both additional source URLs in the row are dead: the FireEye APT40 URL now redirects to cloud.google.com/security/mandiant and the IntrusionTruth URL returns 404, so archived snapshots opened during this task are cited for those. Rows 456, 1979 and 2573 also describe APT40/TEMP.Periscope but different victims (an unnamed organisation in the 2022 ASD advisory, Philippine justice/law-firm targets 2015, and a broad 2014+ multi-country campaign); no same-victim history was found for row 260. RM34 and RM21 were considered and dropped on their exclusion clauses (detection was prompt and by the victim itself; the earlier campaigns are recorded as attempts with no documented unremediated comparable weakness). Sector: the primary report describes the victim as a company that provides specialist engineering solutions, mapped to M; a C (manufacturing) mapping is arguable if the company manufactures rather than provides engineering services.