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

ADT Inc. — April 2026 breach

Clustered 8 records across 6 jurisdictions: 6 filings and 2 leak-site claims · filing window Apr 24, 2026 → Jul 29, 2026. View entity profile → Other incidents for this victim →

✓ affected count, data types, discovery date agreeMerge100%

Determination

Confirmed

Members

8 records

States

6

Affected · reported

331,536

First → last filing

Apr 24, 2026 → Jul 29, 2026

Merge confidence

100%

incident inc_b7aeab6275ce4a1f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 2 unverified claims. Intrusion Apr 20, 2026, discovered Apr 20, 2026 — the first regulatory filing landed 4 days later; 4 later filings were flagged late. 331,536 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 96-day schedule across 6 filings beginning Apr 24, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
4days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Same day

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
96days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMassachusetts✗ MA AG >90dTexas✗ TX AG >30dWashington✗ WA AG >90dOregon✗ OR AG >45dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 20, 2026breach begins
Apr 20, 2026discovered
notification delay · 4 days
Apr 24, 2026first filing
Jul 29, 2026most recent filing

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

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

  1. APR 24DE AGDE AG noticefirst filing · no count statedday 0
  2. APR 24Leak siteshinyhunters postattacker claim · unverifiedday 0
  3. JUL 27MA AGMA AG notice4,540 MA residents+94d
  4. JUL 28TX AGTX AG noticestates nationwide total 331,536+95d
  5. JUL 28WA AGWA AG notice5,129 WA residents+95d
  6. JUL 28OR AGOR AG noticestates nationwide total 331,536+95d
  7. JUL 29NH AGNH AG noticestates nationwide total 331,536+96d
  8. AUG 23Leak sitelockbit5 postmost recent · attacker claim · unverified+121d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 20, 2026
TX AG
Discovered
Apr 20, 2026
DE AG + MA AG + TX AG +3
Data types
Identity (basic) · Government ID
DE AG + MA AG + TX AG +2
Attack vector
Unauthorized Access
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)

331,536

Sum of filed state slices

42,917· 12.9% of stated

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

US331,536
TX32,546
WA5,129
MA4,540
NH702

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 claim2 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing6 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 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

96 days

Cadence

~1 / 19.2d

vs. multi-state median

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