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 →
Internet outages at major providers are sometimes deliberately caused by attackers hijacking accounts or destroying infrastructure, with recovery ranging from hours to days.
Miasma botnet malware reached developers through compromised open-source packages, stealing credentials and cloud access tokens from infected machines across three coordinated campaigns in 2026.
Daxin and its new Stupig backdoor persisted undetected for 13 years, exploiting outdated Java software to infiltrate Taiwan’s high-tech manufacturing sector.
Millions of developers received malware through compromised npm packages; rotate credentials and audit systems immediately if your projects depend on AsyncAPI, Keyv, Axios, or @ctrl/tinycolor.
After healthcare data breaches, most major organizations offer one to two years of free credit monitoring and identity theft protection, though federal law doesn’t require it.
Treasury sanctions VPN operator and cybercriminal suppliers for enabling 25+ ransomware groups targeting U.S. hospitals, governments, and financial firms.
Large enterprises and U.S. healthcare organizations face accelerating ransomware targeting, with enterprise attacks up 74% and healthcare enduring 2.3 attacks daily in H1 2026.
The attack exploits developer trust in open-source repositories.
Attackers can hijack Windows Defender using symbolic links, requiring only admin access and built-in Windows commands, leaving minimal forensic traces.
Learn what Dark Basin proved, what remains alleged, and how targeted climate groups can reduce phishing risk.
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.