DEXCOM, INC.
bd_38196c8851a91c18 · schema v1 · pii pii-v2
Full breach record for DEXCOM, INC. →3 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Redact 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
Sector: Medical Equipment | Revenue: $4.97B USD
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 10, 2026
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- California State AGbd_1605ecaea23bf1532026-06-12 · +120dVerified
- New Hampshire State AGbd_776fb90ed215b9e22026-06-12 · +120dVerified
- Nebraska State AGbd_b7744581e1d27ccc2026-06-12 · +120dVerified
- Massachusetts State AGbd_c65511a6a83cc3732026-06-12 · +120dVerified
Filing propagation · 4 filings · 4 states
View merged incident ↗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.