DexCom Listed as Ransomware Victim by Redact
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Ransomware group Redact claims a breach of medical device maker DexCom, exposing employee and third-party credentials.
Ransomware.live has indexed a victim listing attributed to a group identified as "Redact," naming DexCom, a manufacturer of continuous glucose monitoring devices, as a target. The posting is a leak-site entry rather than a detailed technical report, and provides only aggregate figures: 29 compromised employee accounts, 4,415 compromised user records, 112 third-party employee credentials, and 114 external attack surface findings associated with DexCom's domain. No stolen data, file samples, or technical indicators of compromise are included in the source material, and the method of initial compromise is not described.
For defenders, this is a notification of inclusion on a ransomware group's claimed victim list rather than a technical breakdown of an attack chain. Organizations in the medical device and healthcare technology space should treat this as a prompt to review exposure of employee credentials (including on infostealer logs, which the source references as a related risk vector), monitor for anomalous third-party access, and check external attack surface exposure. Given the lack of corroborating technical detail, confidence in attribution to a specific named threat actor and in the scope of the claimed breach should remain low until further evidence or confirmation from DexCom or independent researchers is available.
Mentioned in this report
Detection guidance
1 detection for this report is in the app — rules that match its indicators, converted to Splunk SPL, to Elastic where their fields map onto Elastic's integrations and to Microsoft Defender XDR KQL wherever Defender records the activity, plus YARA and Suricata. Three days of it free, no card.
Source reporting: https://www.ransomware.live/id/RGV4Q29tQFJlZGFjdA==
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs