← Breach analysis by the Dual Vulnerabilities framework

Halliburton Cyberattack (Unattributed, 2024)

2024 · United States · B - Mining and quarrying · Cyberattack with IT disruption and data theft

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Cyberattack with IT disruption and data theft

Dual vulnerability type

Strategy to Execution

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

Decisive stage: response (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) Halliburton is a US oilfield-services company designated critical infrastructure, running a formal incident-response capability: its own SEC filings state a cybersecurity response plan existed and was activated, and publicly commit that the company is communicating with its customers and other stakeholders regarding the incident. (2) In practice, attackers gained access by 21 August 2024; although the company isolated systems proactively, portions of business applications (invoicing, purchase orders) were disrupted for days, and data was exfiltrated - acknowledged only in a second 8-K on 3 September, when the company was still evaluating what information had been taken; customers meanwhile reported being left in the dark about whether and how the attack impacted them, and some cut their connections to Halliburton and obtained technical indicators via the ONG-ISAC. (3) The classification rests on the response/disclosure stage: the expectation was doctrinal - stated publicly by the company in its 8-K filings - and the break was in execution, because the declared stakeholder communication was not operationalised for the partners actually exposed; doctrine and execution therefore diverged diagonally (Strategy to Execution), rather than leadership having failed to decide anything. The entry vector and the detection method are undisclosed and are not load-bearing; the egress gap (data exfiltrated without the company initially knowing) is a reading of the filings rather than a documented control failure, so it contributes only as inference, and no source shows the technical response itself (isolation, Mandiant forensics, law-enforcement notification) malfunctioned. (4) RM39 (Strategy to Execution lens): the notification commitment lived in the filings, but the notification workflow was never operationalised for partners - market disclosure was prompt and accurate, yet directly exposed customers received nothing sufficient to determine their own exposure (causal role: Constraining). RM43 (Strategy to Execution lens): remediation toward affected partners was not operationalised after the breach - customers were left without the information needed to assess impact and protect themselves, some disconnecting from Halliburton's systems and relying on ONG-ISAC coordination instead of company communication (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Dataset discrepancies (kept out of the numbers): the row description says the attack cost $35,000, but reporting on the Q3 disclosure says about $35 million; eurepoc_extra economic_impact_value 35000 matches the row's apparent magnitude error. eurepoc_extra also records no system interference/disruption and no data breach/exfiltration, which the company's own Item 1.05 8-K of 3 September 2024 contradicts (business-application disruption and confirmed exfiltration). Attribution: Halliburton never publicly named an actor; the RansomHub link rests on BleepingComputer's analysis of an indicator from Halliburton's 26 August supplier communication, and RansomHub did not claim the victim; a ransom demand around $45 million was reported but unverified, and no payment was ever established. The TechCrunch follow-up URL from the search results could not be opened (404) and is not cited. No related_rows in the case file and no earlier Halliburton result in the output directory. Link check: sec.gov blocks automated access (HTTP 403); the page was opened and read during research. RM35 Egress / exfiltration monitoring gap was considered for the egress gap but not coded: no source establishes that egress visibility or prevention should have existed there, so the condition is described in the rationale instead.