HESS CORPORATION
bd_4e1edb9289abda9c · schema v1 · pii pii-v1
Full breach record for HESS CORPORATION →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Dispossessor on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
hess.com
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 19, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitecl0pbd_f1c17299a649ce902023-07-14 · +280dCandidate
Regulatory filings (1) · sorted by filing gap
- Vermont State AGbd_8a7abaf95ded45bb2023-07-20 · +274dVerified by operator
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Jul 20 (VT), last Apr 19 — a 274-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
dispossessor
According to ransomware.live, This is not a ransomware group but a data broker