DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed18 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedembargohigh sensitivity
Merged incident · 18 filings

NCH CORPORATION — August 2025 breach

Clustered 18 filings across 10 jurisdictions · filing window Nov 21, 2025 → May 5, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

18 filings

States

9

Affected · reported

4,732

First → last filing

Nov 21, 2025 → May 5, 2026

Merge confidence

100%

incident inc_dba9614d10e64436 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 16 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Aug 1, 2025–Feb 25, 2026, discovered Aug 1, 2025 — the first regulatory filing landed 122 days later. 4,732 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Employment, and 6 more. Notifications rolled out on a 164-day schedule across 16 filings beginning Nov 21, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
122days

Discovered → first regulatory filing

Discovery variance
244days

Range of discovered_at dates across filings

Leak precedence
9days before filing

Days between the first leak-site claim and the first regulatory filing. 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
164days

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 · 53dLeak gap⏱ Leak >90dVermont✓ VT AG ≤14 bdayMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Aug 1, 2025breach begins
Aug 1, 2025discovered · members disagree
notification delay · 122 days
Dec 1, 2025first filing
May 5, 2026most 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. NOV 21Leak sitecl0p postfirst filing · attacker claim · unverifiedday 0
  2. DEC 1IL AGIL AG noticeno count stated+9d
  3. DEC 5VT AGVT AG noticeno count stated+13d
  4. DEC 5MA AGMA AG notice33 MA residents+13d
  5. DEC 5NH AGNH AG notice8 NH residents+13d
  6. DEC 5MT AGMT AG notice6 MT residents+13d
  7. DEC 5NE AGNE AG notice13 NE residents+13d
  8. DEC 5ME AGME AG notice2 ME residents+13d
  9. DEC 5IN AGIN AG noticestates nationwide total 3,912+13d
  10. DEC 9TX AGTX AG noticestates nationwide total 3,912+17d
  11. MAR 9Leak siteembargo postattacker claim · unverified+108d
  12. MAY 1VT AGVT AG notice1 VT residents+160d
  13. MAY 1ME AGME AG notice5 ME residents+160d
  14. MAY 1NH AGNH AG notice10 NH residents+160d
  15. MAY 1MA AGMA AG notice38 MA residents+160d
  16. MAY 1NE AGNE AG notice29 NE residents+160d
  17. MAY 1IN AGIN AG noticestates nationwide total 4,732+160d
  18. MAY 5TX AGTX AG noticemost recent · states nationwide total 4,732+164d
  19. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 1, 2025 – Aug 31, 2025
VT AG
Discovered
Aug 1, 2025NE AGNov 25, 2025IL AG + VT AG + MT AG +2Mar 9, 2026ME AG + NH AG + NE AGApr 2, 2026TX AGfilings disagree on discovery
Data types
Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
IL AG + VT AG + MA AG +5
Attack vector
Unauthorized Access
VT 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,732

Sum of filed state slices

2,338· 49.4% of stated

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

US4,732
TX2,082
IN167
MA38
NE29
NH10
MT6
ME5
VT1

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 filing16 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 25, 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

164 days

Cadence

~1 / 9.6d

vs. multi-state median

20.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.