TRENDING
Vintage silver stopwatch with a chain on a black background, its dial showing seconds from 5 to 60
October 28, 2026
How to Find a Slow Query in PostgreSQL 18 With pg_stat_statements, Read Its EXPLAIN ANALYZE Plan, and Fix It With the Right Index
A wooden Tower of Hanoi puzzle on a market table, with three pegs and stacked discs of different sizes
October 28, 2026
Two Labs’ Claimed Refutations of the Exponential Time Hypothesis Turn Verification Into a Statement-Reading Problem, and Their Lean Theorems Promise Only That a Constant Exists
Two earthworms lying together on wet brown leaf litter, photographed close up
October 28, 2026
Tailscale Merged Fixes for Most of the 11 “Tailworm” Findings Before Shipping a Release, and the Forwarding Switch It Recommends Already Exists in the Shipped Client
Unpopped corn kernels mixed with popped popcorn on a white surface
October 28, 2026
How to Stop Decompression Bombs in Python With Hard Output Limits for gzip, Brotli, zstd, ZIP, and tar.gz
Ouroboros, a polished stainless steel sculpture of two interlocking loops with a pierced surface, standing beside a dark pool under trees
October 28, 2026
Anthropic’s S-1 Puts Safety Audits Inside the “Closing the Loop” Cycle It Warns About, and Says Its Evaluations Could Overstate Safety
28 Oct 2026
SXZ.io SXZ.io
  • Home
Search the Site
Popular Searches:
Technology Amazon AI
Recent Posts
A mountain gorilla looks at the camera from green forest undergrowth
How to Compress Time-Series Metrics in Python With Gorilla Delta-of-Delta and XOR Encoding
October 28, 2026
A bronze-framed hourglass with white sand beside a small Ferris wheel ornament on a wooden table against a teal wall
NIST’s Final Post-Quantum Transition Report Puts Every Quantum-Vulnerable Public-Key Scheme on One 2030 and 2035 Clock, and Three Federal Documents Word the Deadline Three Ways
October 28, 2026
Six weathered stone columns of the Temple of Apollo at Delphi, Greece, standing on a stone platform above a valley of olive groves
Honeypots Recorded Probes Against Oracle E-Business Suite CVE-2026-101767 Seven Days After Its Patch, and the Finder’s Write-Up Is Dated Patch Day
October 28, 2026
SXZ.io SXZ.io
  • Home

Categories

Articles 269 Posts
News 272 Posts
Learning Hub 242 Posts
Home/News/Have I Been Pwned Finds Half of ShinyHunters’ Carhartt Breach Data Was Synthetic
News

Have I Been Pwned Finds Half of ShinyHunters’ Carhartt Breach Data Was Synthetic

An AI-assisted review by Have I Been Pwned's Troy Hunt found that ShinyHunters padded its Carhartt breach claim with millions of synthetic records, cutting the real number of affected people nearly...

August 26, 2026 4 Min Read
195

Workwear retailer Carhartt is the latest company caught up in a ShinyHunters extortion campaign, but the breach turned out to be a lesson in verification as much as a security incident. When Troy Hunt, the researcher behind Have I Been Pwned (HIBP), ran the leaked data through his usual analysis process this week, he found that roughly half of the records ShinyHunters dumped were not real people at all. An AI-assisted review cut his working estimate from just under 25 million addresses to 12,933,413, a number Hunt says would have looked twice as bad if he had stopped at the first pass.

Table Of Content

  • A familiar extortion playbook
  • How an AI-assisted review caught the padding
  • What the synthetic records looked like
  • The real numbers, and what was actually exposed
  • Why the process matters as much as the number

A familiar extortion playbook

ShinyHunters announced the Carhartt breach on August 13, claiming to have stolen more than 50GB of compressed data that included customer records, employee information, customer metadata, and loyalty program details. According to The Register, the group said it published the data after Carhartt hired what the criminals called “a very unskilled and incompetent negotiator” to talk them down from a $3.3 million extortion demand. That framing comes from ShinyHunters itself; Carhartt has not confirmed or disputed it, and the company did not respond to The Register’s request for comment or say anything publicly about the incident.

Carhartt, the 1889-founded workwear brand now headquartered in Dearborn, Michigan, has expanded well beyond its blue-collar roots in recent years through its Carhartt WIP streetwear line, giving it a much larger and more international customer base than its original tradespeople-and-outdoor-workers audience.

How an AI-assisted review caught the padding

Hunt’s own account of the analysis, published August 26, describes his standard HIBP workflow: run the open source Email Address Extractor tool over a leaked corpus, get a count of unique addresses, and use that number to help prioritize processing. For Carhartt, that first pass returned 24,876,077 unique addresses, a figure that happened to line up with what other sites were already reporting about the breach’s scale, which initially reinforced Hunt’s impression that the whole dump was legitimate.

This time, Hunt also ran the data through an AI agent called OpenClaw, which he had already been using for various tasks throughout the year and nicknamed “PwnedClaw” for this particular session. The assistant flagged that the underlying files followed the TPC-DS schema, an industry-standard benchmark format used to generate synthetic test data for retail analytics systems, and that the data had come from Carhartt’s customer analytics warehouse in Databricks rather than a production transactional database. Rather than take that flag at face value, Hunt went back and pulled real examples from the data to confirm or disprove it.

What the synthetic records looked like

The evidence, once Hunt went looking, was hard to miss:

The corpus contained roughly 4 million .edu addresses and 3.9 million .org addresses, an abnormally high share for a clothing retailer, including obviously fabricated entries such as addresses on single-letter domains or domains made of random character strings. About 10.1 million domains appeared exactly once each across the whole dataset. Real breach data from a retail company typically follows a power-law pattern, with a relatively small number of common personal and corporate email domains accounting for a large share of addresses; a dataset dominated by one-off domains is a signature of synthetic generation instead.

The birth-country field was even more telling: it spread almost evenly across 211 countries at roughly 380 to 420 records each, with the United States appearing only 407 times, tied with Canada and dwarfed by countries such as Antigua and Barbuda and Lesotho. Birth years told the same story, spread uniformly across 1924 to 1992 at roughly 1,050 to 1,194 records per year, every single year, with no weighting toward any real population curve. Both patterns are what you would expect from a random number generator sampling a fixed range, not from an actual customer base concentrated in the United States and Europe.

The real numbers, and what was actually exposed

After stripping out the synthetic TPC-DS records, Hunt did a further round of manual cleanup, removing duplicate entries and tens of thousands of addresses on a Carhartt-linked suppression domain whose aliases were tagged “perftest,” marking them as internal performance-testing accounts rather than real customers. That left a final count of 12,933,413 accounts he assessed as genuine. That is the figure now listed on the Have I Been Pwned breach page for Carhartt, added to the service on August 25. The compromised data associated with those accounts includes email addresses, names, phone numbers, and physical addresses; the customer login field in the source data was empty, meaning no passwords were part of this exposure.

HIBP also found that 83 percent of the genuine addresses were already logged in the service from earlier, unrelated breaches, meaning the incremental new exposure from Carhartt is smaller still than the headline 12.9 million figure suggests.

Why the process matters as much as the number

Hunt was blunt about the lesson in his write-up: “You’re not going to believe this, but turns out you can’t always take criminals at their word.” His broader point is aimed at anyone who repeats a breach’s claimed scale without checking it themselves: “take headline numbers with a grain of salt unless you’re confident in the processes of those making the claims.”

The irony is not lost in the details. An AI assistant helped Hunt spot the pattern that something was wrong with the data in the first place, but the actual verification, pulling real examples, checking birth-country and domain distributions, and confirming the numbers by hand, was still manual work. For the roughly 12.9 million people whose real information was exposed, the practical advice is the same as any other breach: be alert to phishing attempts that use your name, email, phone number, or address to appear legitimate, and check whether your email address appears in this or other breaches through HIBP directly.

Tags:

Artificial IntelligenceCybersecurityData BreachesHave I Been PwnedShinyHunters

Share

A page from the Codex Arabicus, a real palimpsest manuscript from Mt. Sinai with 5th-century Syriac text scraped away and overwritten with Arabic text around 900 AD
Previous Post

How to Remove a Leaked API Key From Git History With git filter-repo

A curved industrial roller conveyor system branching into multiple paths inside a factory
Next Post

Red Hat’s Jira Automation Rebuild Turns Agent Autonomy Into a Reliability Problem

No Comment! Be the first one.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Latest
28 Oct
How to Compress Time-Series Metrics in Python With Gorilla Delta-of-Delta and XOR Encoding
28 Oct
NIST’s Final Post-Quantum Transition Report Puts Every Quantum-Vulnerable Public-Key Scheme on One 2030 and 2035 Clock, and Three Federal Documents Word the Deadline Three Ways
Trending
October 28, 2026
How to Compress Time-Series Metrics in Python With Gorilla Delta-of-Delta and XOR Encoding
October 28, 2026
NIST’s Final Post-Quantum Transition Report Puts Every Quantum-Vulnerable Public-Key Scheme on One 2030 and 2035 Clock, and Three Federal Documents Word the Deadline Three Ways
October 28, 2026
Honeypots Recorded Probes Against Oracle E-Business Suite CVE-2026-101767 Seven Days After Its Patch, and the Finder’s Write-Up Is Dated Patch Day
October 27, 2026
How to Find a Slow Query in PostgreSQL 18 With pg_stat_statements, Read Its EXPLAIN ANALYZE Plan, and Fix It With the Right Index
October 27, 2026
Two Labs’ Claimed Refutations of the Exponential Time Hypothesis Turn Verification Into a Statement-Reading Problem, and Their Lean Theorems Promise Only That a Constant Exists
October 27, 2026
Tailscale Merged Fixes for Most of the 11 “Tailworm” Findings Before Shipping a Release, and the Forwarding Switch It Recommends Already Exists in the Shipped Client

Related Posts

Rows of server racks in a data center representing network infrastructure targeted by botnets
News

C0XMO Botnet Shows Why Old Router Firmware Still Matters

June 7, 2026
Close-up of a USB flash drive, representing physical data-theft risk in office security incidents
News

Fake IT Support Is Now Walking Through the Front Door

June 7, 2026
A phone security app on a smartphone resting on a laptop keyboard.
News

Everest Forms Pro Flaw Is Being Exploited to Create Rogue WordPress Admins

June 7, 2026
A phone secured by a padlock, illustrating AI data-leak containment and security controls.
News

OpenAI’s Lockdown Mode Is a Data-Leak Brake, Not a Prompt-Injection Cure

June 8, 2026
SXZ.io SXZ.io
  • [email protected]

Categories

Articles
Learning Hub
News

All Rights Reserved by SXZ.io ©2026