DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed12 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 12 filings

HANESBRANDS INC. — May 2022 breach

Clustered 12 filings across 9 jurisdictions · filing window Aug 16, 2022 → Nov 30, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

75,106

First → last filing

Aug 16, 2022 → Nov 30, 2022

Merge confidence

100%

incident inc_531cf4247d084926 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion May 24, 2022–Jun 6, 2022, discovered May 24, 2022 — the first regulatory filing landed 84 days later (flagged late). 75,106 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 4 more. Notifications rolled out on a 106-day schedule across 12 filings beginning Aug 16, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
84days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
106days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 190dOregon✗ OR AG >45dWashington✗ WA AG >90dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 24, 2022breach begins
May 24, 2022discovered
notification delay · 84 days
Aug 16, 2022first filing
Nov 30, 2022most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 16MA AGMA AG noticefirst filing · 447 MA residentsday 0
  2. AUG 16MT AGMT AG notice37 MT residentsday 0
  3. AUG 16IN AGIN AG noticestates nationwide total 75,106day 0
  4. AUG 16CA AGCA AG noticeno count statedday 0
  5. AUG 16ME AGME AG notice109 affectedday 0
  6. AUG 17SC AGSC AG notice4,603 SC residents+1d
  7. SEP 30OR AGOR AG noticeno count stated+45d
  8. NOV 23WA AGWA AG notice644 WA residents+99d
  9. NOV 29NH AGNH AG noticeno count stated+105d
  10. NOV 29OR AGOR AG noticeno count stated+105d
  11. NOV 29CA AGCA AG noticeno count stated+105d
  12. NOV 30ME AGME AG noticemost recent · 186 affected+106d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 24, 2022
IN AG
Discovered
May 24, 2022
MT AG + CA AG + ME AG +4
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + MT AG + CA AG +4
Attack vector
Ransomware
MT 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)

75,106

Sum of filed state slices

6,348· 8.5% of stated

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

US75,106
SC4,603
WA644
MA447
IN431
ME186
MT37

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 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 Jun 12, 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

106 days

Cadence

~1 / 9.6d

vs. multi-state median

13.3× 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.