← Breach analysis by the Dual Vulnerabilities framework

Levare International ransomware and data-theft extortion (Medusa, 2023)

2023 · United Arab Emirates · C - Manufacturing · Ransomware attack with data theft and DDoS extortion pressure

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with data theft and DDoS extortion pressure

Dual vulnerability type

Strategy to Leadership

Evidence coverage: 3/6 stages, weight 17/60

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

Why this classification

(1) Strategic expectation: as an oil-and-gas equipment manufacturer with US operations, Levare was bound to notify affected former employees and state attorneys general accurately about a breach of their personal data, and during the extortion its negotiators held direct knowledge of the attacker's identity and demands. (2) In practice: Medusa entered the US (Houston) IT systems in late July 2023, accessed company data including historical payroll files, and after negotiations collapsed took levare.com offline with DDoS attacks (1-5 August, again around 14 August) and listed the victim on its leak site on 14 August with a 500,000 USD demand; the company's own notification letter, however, describes an August 2 data breach by an unknown group that placed malware on servers, calls it a generic incident, lists only name, address, SSN and banking details, and states it is not clear what information was seen or downloaded, while no public statement appeared despite press inquiries. (3) The entry vector is undisclosed and not load-bearing; the classification rests on the response/disclosure stage: the expectation (accurate notification) is doctrinal, and the chain broke at leadership communication - what the organisation knew internally (a self-identified group in negotiation, data published with proof screencaps) diverges from the narrative its own disclosure artefacts told affected individuals and the regulator. That is a gap within the doctrinal column, not a control that policy failed to realise in operations; the egress and recovery conditions (unscoped exfiltration, a website repeatedly downed by DDoS) are a secondary Expertise to Execution pattern but rest on inference. RM39 (Strategy to Leadership lens): leadership's disclosure behaviour diverged from the legal expectation of an accurate notification - the victim's own letter recast a self-attributed, publicly posted ransomware extortion as an incident by unknown parties, and disclosure only came after the attacker's leak site forced it (causal role: Constraining). RM33 (Strategy to Leadership lens): the forensic inability admitted in the letter - it is not clear what information was seen or downloaded - left the loss unscoped and the notification necessarily incomplete, and no source shows leadership requiring the forensic readiness that incident and legal strategy depends on (causal role: Obscuring). RM32 (Strategy to Leadership lens): no availability objective or mitigation arrangement is documented, and routine DDoS attacks knocked the company's public web presence offline for days at the extortioners' choosing, which is how the absence of an availability posture for critical services under adversarial load showed up (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

Data quality: the Victim / receiver fields carry the same name twice (Levare International Ltd.;Levare International Ltd.), and receiver_category lists Critical infrastructure (Energy;Critical Manufacturing); the company manufactures electric submersible pumps, hence C Manufacturing. Provenance: the incident narrative and most detail (1TB exfiltrated, passport copies, negotiation interruption) come from SuspectFile, which relays Medusa's own claims - treated as unverified attacker claims; the databreaches.net article independently confirms the leak-site listing, the 500,000 USD demand and the DDoS downtime, and Strauss Borrelli's 24-08-2023 investigation page independently confirms the notification letters to former employees repeating the generic malware framing. The Montana AG-hosted notification letter is the victim's own primary disclosure. Date discrepancy: Medusa claims entry on 25-07-2023, the victim's letter dates the breach 02-08-2023. Comparitech's incident ledger lists the ransom as not paid but draws on a single publisher. Security policy: the Medusa leak site itself was not accessed; leak-site aggregators found in searches were not cited. Link check: dojmt.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research. Link check: suspectfile.com blocks automated access (HTTP 403); both pages were opened and read during research. Unattended run: no consent-gated actions were needed or taken.