2023 · United States · C - Manufacturing · Ransomware attack with data theft
Analysed 2026-11-06 by Hermes
Open this case in the tool →Ransomware attack with data theft
Expertise to Execution
Evidence coverage: 4/6 stages, weight 34/60
Decisive stage: detection (clearest evidence) · Alternative: Strategy to Execution
(1) BHI Energy (BHI Energy | Specialty Services LLC, Weymouth, Massachusetts, a Westinghouse Electric subsidiary providing specialty services and staffing to nuclear, fossil, hydro, wind and solar generation, recorded in EuRepoC as critical infrastructure / critical manufacturing) was expected to authenticate and monitor remote access - including third-party contractor access - to cover its estate with endpoint detection, and to notice bulk data leaving its network; its own post-incident remediation shows it treated exactly these controls as the baseline expectation. (2) In practice a previously compromised third-party contractor account logged in over VPN on 30 May 2023 without MFA, spent a month inside undetected - two reconnaissance passes, staging on a BHI server, domain-level credentials obtained - exfiltrated 690GB including a copy of the Active Directory database over nine days unnoticed, and only the ransomware encryption on 29 June revealed the intrusion; recovery and disclosure, by contrast, were sound (unaffected cloud backups, no ransom, prompt eradication, detailed self-disclosure). (3) The knowing-doing gap sits in the material column: every missing control was a standard technical remedy within the organisation's own toolset - BHI implemented VPN MFA, extended its own EDR/AV estate and reset all passwords within days of eradication - and no source documents a strategic policy that existed and was not realised (Strategy to Execution) or a leadership decision that deferred or under-funded these controls (Strategy to Leadership); the remedies were known and knowable but never executed in operations and architecture, which is Expertise to Execution. The classification rests on the detection stage (its own notification documents both the 30-day time-to-detect and the post-incident extension of the EDR capability that should have caught the intrusion); the entry vector is documented and load-bearing but points to the same type, and no stage points to a different DV-Type, so no tie-break was needed. (4) RM34 (Expertise to Execution lens): detection tooling that existed was not deployed, configured or maintained to catch the intrusion - EDR/AV was only extended across the environment after the incident, and a 30-day dwell ended with discovery at the encryption moment rather than by monitoring (causal role: Obscuring). RM22 (Expertise to Execution lens): the contractor VPN account authenticated with no MFA and its compromise went unmonitored, an identity control the organisation's own remediation proved feasible but had never implemented (causal role: Enabling). RM13 (Expertise to Execution lens): trust in third-party contractor access was not matched by assessment or monitoring - the account BHI relied on was already compromised, and its two reconnaissance passes over the trusted path triggered nothing on the victim side (causal role: Enabling). RM35 (Expertise to Execution lens): egress visibility was not realised in operations - archives were staged on BHI's own server and 690GB left over nine days undetected, with the victim learning the volume only from the attacker's file listing (causal role: Amplifying). The lateral climb to domain-level credentials (directory-hygiene path, AD database copied) is documented from the notification timeline but rests on analyst reading of it, so it is described here rather than carried further; recovery and response show alignment and are not coded.
RM34 — Monitoring / detection / alert-handling gapRM22 — Authentication / credential exposureRM13 — Third-party / supply-chain trust boundaryRM35 — Egress / exfiltration monitoring gapVictim as written in the row: 'BHI energy'; formal name per the notification letter: BHI Energy | Specialty Services LLC, Weymouth, Massachusetts, subsidiary of Westinghouse Electric Company. Primary source is BHI's own 18 Oct 2023 breach notification (K&L Gates letter) to the Iowa Attorney General, read via DocumentCloud; BleepingComputer (23 Oct 2023) reported it. Timeline in the row description matches the notification. Total affected: 896 Iowa residents per the notification; at least 91,269 individuals overall per state filings as reported by SC Media/teiss. Akira had not leaked the data on its extortion portal at reporting time (BleepingComputer), so the disclosure was victim-initiated. The notification-letter delay (breach discovered 29 June, affected individuals identified 1 September/4 October, notices 18 October) reflects the forensic review of 767k files; no source treats it as an unreasonable or concealed disclosure, so no notification marker is coded. Sector: EuRepoC codes the receiver as Critical infrastructure / Critical Manufacturing and the company describes itself as services and staffing for the power generation markets; 'C Manufacturing' follows the dataset's own subcategory. The 'lateral movement to obtain domain-level credentials' detail (containment stage) is an analyst reading of the notification timeline (Uptycs via SC Media), hence the containment stage carries secondary source weight.