CDK Global Ransomware Investigation Guide: Evidence, Notices, and Verification
A source-by-source breakdown of the CDK Global ransomware evidence, the single official breach notice on file, and how to check your own exposure.

Who was breached, what was exposed, and what to do about it.
Hashed in your browser - only five characters of the hash are ever sent.
1,000+ catalogued breaches: the date, the account count, and exactly what was exposed.
Tick what was leaked and get the steps in order, each linked to the rule behind it.
All three bureaus, plus the four registries a credit freeze does not cover.
Tips to protect your data and privacy
Browse →484 guidesBreaking news on recent data breaches
Browse →287 guidesAll the latest and largest data breaches
Browse →229 guidesIdentity theft prevention and news
Browse →203 guidesData breaches at technology companies
Browse →139 guidesData breaches affecting retail and e-commerce companies
Browse →A source-by-source breakdown of the CDK Global ransomware evidence, the single official breach notice on file, and how to check your own exposure.
A control-by-control breakdown of the 2024 Ascension ransomware attack, from the single downloaded file to the six-week EHR outage.
The MoJ widened the LAA breach window to 2007–2025 in July 2025 — here’s who that adds, what was taken, and the steps to protect yourself.
A control-by-control breakdown of how one MFA-less Citrix login became a 192.7 million-person breach — and what the $22M ransom actually bought.
A clear read on 2026 ransomware data, who attackers are hitting, the legal risk in paying, and the first calls to make.
Check ransomware claims against SEC 8-K filings, the HHS breach portal and joint advisories, and spot recycled or fake leak data.
The latest FBI ransomware numbers, the new Gunra and Medusa warnings, the first flaws to patch and where to report an attack.
The first-hour ransomware steps, backup checks and sanctions risks to settle before attackers force the decision for you.
Deepfake voice scams cost businesses $893M in 2025. Three defenses—callback verification, pre-agreed codes, and dual approval—work reliably and can be deployed in hours.
Infostealers silently extracted 1.8 billion credentials in 2025 and now operate as cheap criminal subscriptions targeting passwords, cookies, and cryptocurrency wallets.

Breach coverage goes wrong in two directions: inflating an exposure into a certainty, or burying it. We publish the disclosed numbers, name the source, and mark clearly where an investigation is still open and the count may change.

Most people find out from a letter weeks after the fact. These are the steps that still work at that point, in the order they should be done, with what each one does and does not protect.
Primary sources: the breached organization's own notification letter, filings in state Attorney General breach databases, the U.S. Department of Health and Human Services breach portal for healthcare incidents, SEC filings, court records and regulator announcements. Where we cite a figure, that figure comes from one of those documents.
Not necessarily, and the difference matters. Most notices state that an unauthorized party accessed or acquired data. That is a different finding from evidence that the data has been used for fraud. We report which one a given notice supports, and we do not fill the gap with speculation.
No. Only the organization that holds your records can confirm that, and it is required to notify you. What we can do is tell you what was disclosed, who the claims administrator or notification contact is, and what steps are worth taking while you wait.
No. Data Breach Radar is independent reporting. Nothing on this site creates a professional relationship or substitutes for advice from a lawyer, a security professional or your bank. Always verify details against the notice you received.
The site is free to read and carries advertising. Some pages may contain affiliate links, which are disclosed on our Affiliate Disclosure page. Advertisers and affiliate partners have no input into what we cover or what we say about it, and we do not accept payment to include, exclude or soften a breach report.
Email contact@databreachradar.com with the URL and what is inaccurate. Corrections to a published report are made on the page itself. Our approach to sourcing and corrections is set out in the Editorial Policy.