Doxim
bd_17e6adc9ef0b7130 · schema v1 · pii pii-v1
Full breach record for Doxim →3 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group LockBit 3.x 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.
Sanctions caution: LockBit 3.x carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.
Source: Ransomware.live
Post text · scraped from the leak site
Doxim is the customer communications management and engagement technology leader serving highly regulated markets, including financial services, utilities and healthcare. We provide omnichannel communications and payment solutions that maximize custo...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
May 9, 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?Regulatory filings (3) · sorted by filing gap
- South Carolina State AGbd_1de8dde984af2be02024-12-30 · +235dCandidate
- Indiana State AGbd_08edb0dc5bdc800b2025-01-24 · +260dVerified by operator
- Massachusetts State AGbd_d401e4d9fb6834882025-01-31 · +267dVerified by operator
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing May 9, last Jan 31 (MA) — a 267-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.