Skip to main content
Darkfield

Ransomware victim disclosure

← All victims

DexCom

Claimed by Redact · listed 4 hours ago

Today
Age
since listed · data leaked

Status timeline

  1. ListedOct 10, 2026
  2. Data leakeddate unknown

At a glance

Group
Redact
Status
Data leaked
Country
United States
Sector
Healthcare
Listed on leak site
Oct 10, 2026

About the victim

AI dossier — public-source company profile

DexCom, Inc. is a medical device company that manufactures continuous glucose monitoring (CGM) systems for diabetes management. Their products provide real-time glucose readings and personalized insights to support insulin therapy and other diabetes treatments.

Industry
Medical Devices & Diabetes Care

Attack summary

Severity: high — DexCom is a major healthcare company handling sensitive medical device data and patient health information. Confirmed data publication by a ransomware group targeting a regulated medical device manufacturer constitutes high severity, even without explicit enumeration of data categories in this excerpt.

The Redact group claims to have breached DexCom and has published data. The leak post does not specify whether encryption, exfiltration, or both occurred, nor does it detail what specific data categories are at stake.

high

What the group claims

Sector: Medical Equipment | Revenue: $4.97B USD

The leak post

captured from the group's site
- We are REDACT. We are not politically or morally motivated, we are not hacktivists, we do not care the shady white-collar dealings of your company.
- We always operate and negotiate in good faith; if your company files get published, you ignored us, wasted our time, or did not meet our ransom demands. Reach out, negotiate a mutually beneficial agreement, pay the ransom, and your security incident goes away quietly.
- We are not currently taking questions from press, journalists, or researchers. In these cases, we will publish press releases on our . If your company experiences a breach by us, we will reach out to you with our contact information.
- Always verify correspondence with our . If this key is ever rotated, it will be announced on our blog, in a statement signed with the previous key, which will remain available for transparency reasons.
- To simplify verification, we have derived the SHA256 hash of our only Tox ID, and signed it with our PGP key, available . This way, negotiators can verify the Tox they communicate with, while we prevent spam and other unsoliciated messages.

Sources

Source

Indexed 4 hours ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About Redact

Redact is a ransomware group first observed in June 2026 with an apparent financial motivation, having been linked to a limited number of confirmed victims to date. Given the group's recent emergence and low victim count of two confirmed cases, detailed public attribution and technical documentation from CISA, FBI, Mandiant, or equivalent authoritative sources remains limited at this time. Targeting patterns indicate a focus on United States-based organizations, with activity concentrated in the Healthcare and Financial Services sectors — industries frequently targeted due to their sensitivity to operational disruption and the high value of the data they hold. No further details regarding country of origin, affiliation, RaaS infrastructure, specific tooling, encryption methodology, or extortion tactics have been publicly documented by reputable threat intelligence sources as of the time of this writing. Due to the group's nascent operational history and the absence of verified public reporting, a complete technical profile cannot be responsibly constructed; analysts should treat this group as an emerging threat requiring continued monitoring, with the available indicators suggesting deliberate sector targeting consistent with financially motivated ransomware actors. Current status is unconfirmed beyond initial observed activity beginning in June 2026. The group has been linked to 4 public disclosures across our corpus. First observed on a leak site on June 28, 2026; most recent post October 10, 2026. The operation is currently active.

Timeline of this disclosure

  • October 10, 2026DexCom listed by Redact on the group's public leak site

Other recent disclosures by Redact

Redact has been linked to 4 public victims on Darkfield. A sample of the most recent:

See the full Redact dossier →

Sector and geography

This disclosure adds to ransomware activity in the Healthcare sector, which has 2,610 disclosures indexed across all operators we track. Geographically, DexCom is reported in United States, a country with 3,176 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Redact means DexCom appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Report the incident to your national CERT, CISA (United States), as required for your jurisdiction.
  • Monitor for the data appearing on Redact's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.