DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed15 records · 14 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedshinyhuntershigh sensitivity
Merged incident · 15 records

TransUnion — July 2025 breach

Clustered 15 records across 14 jurisdictions: 14 filings and 1 leak-site claim · filing window Aug 26, 2025 → Sep 4, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 records

States

14

Affected · reported

4,461,511

First → last dated filing

Aug 26, 2025 → Sep 4, 2025

Merge confidence

100%

incident inc_bd022475fabd4f52 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings and 1 unverified claim. Intrusion Jul 28, 2025–Jul 29, 2025, discovered Jul 29, 2025 — the first regulatory filing landed 28 days later. 4,461,511 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 9-day schedule across 13 dated filings beginning Aug 26, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
28days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 38d

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
9days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMaine✓ ME AG ≤30d · 28dIowa✓ IA AG ≤5 bdayTexas✓ TX CRA notice dueSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 28, 2025breach begins
Jul 29, 2025discovered · members disagree
notification delay · 28 days
Aug 26, 2025first dated filing
Sep 4, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JUN 28Leak siteshinyhunters postfirst record · attacker claim · unverifiedday 0
  2. AUG 26IN AGIN AG noticestates nationwide total 4,461,511+59d
  3. AUG 26WI AGWI AG noticestates nationwide total 4,461,511+59d
  4. AUG 26DE AGDE AG noticeno count stated+59d
  5. AUG 27ME AGME AG noticestates nationwide total 4,461,511+60d
  6. AUG 27CA AGCA AG noticeno count stated+60d
  7. SEP 1VT AGVT AG noticeno count stated+65d
  8. SEP 2IA AGIA AG notice25,943 IA residents+66d
  9. SEP 2OR AGOR AG noticestates nationwide total 4,461,511+66d
  10. SEP 3MT AGMT AG notice9,410 MT residents+67d
  11. SEP 4TX AGTX AG noticestates nationwide total 4,461,511+68d
  12. SEP 4SC AGSC AG notice78,834 SC residents+68d
  13. SEP 4MA AGMA AG notice95,336 MA residents+68d
  14. SEP 4NH AGNH AG noticemost recent · 16,508 NH residents+68d
  15. SEP 8NE AGNE AG noticefiling day not on record · no count stated—
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 28, 2025
IN AG
Discovered
Jul 29, 2025TX AGJul 30, 2025ME AG + IA AG + NH AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
WI AG + IA AG + TX AG +9
Attack vector
Third-Party / Supply Chain
DE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

4,461,511

Sum of filed state slices

778,370· 17.4% of stated

83% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US4,461,511
TX377,357
MA95,336
IN88,898
SC78,834
WI69,256
IA25,943
ME16,828
NH16,508
MT9,410

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing14 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

9 days

Cadence

~1 / 0.8d

vs. multi-state median

1.5× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.