DisclosureLens
State AGConfirmed14 filings · 14 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 14 filings

THE CORNWELL QUALITY TOOLS COMPANY — December 2024 breach

Clustered 14 filings across 14 jurisdictions · filing window Sep 1, 2025 Sep 9, 2025. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

14 filings

States

14

Affected · reported

103,782

First → last filing

Sep 1, 2025 Sep 9, 2025

Merge confidence

100%

incident inc_3ec7233149594484 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. Intrusion Dec 12, 2024–Dec 20, 2024, discovered Dec 20, 2024 — the first regulatory filing landed 255 days later (flagged late). 103,782 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 8-day schedule across 14 filings beginning Sep 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
255days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
8days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont VT AG >45 bdayWashington WA AG >90dCalifornia CA 60-day late · 258dMaine ME AG >90d · 262dOregon OR AG >45dTexas TX AG >30dIowa IA AG ≤5 bdayMassachusetts MA credit monitoring dueSouth Carolina SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 12, 2024breach begins
Dec 20, 2024discovered
notification delay · 255 days
Sep 1, 2025first filing
Sep 9, 2025most 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. SEP 1IL AGIL AG noticefirst filing · no count statedday 0
  2. SEP 4IA AGIA AG notice616 IA residents+3d
  3. SEP 4MT AGMT AG notice209 MT residents+3d
  4. SEP 4VT AGVT AG noticeno count stated+3d
  5. SEP 4NE AGNE AG notice1,230 NE residents+3d
  6. SEP 4IN AGIN AG noticestates nationwide total 103,782+3d
  7. SEP 5WA AGWA AG notice3,170 WA residents+4d
  8. SEP 8NH AGNH AG notice1,164 NH residents+7d
  9. SEP 8MA AGMA AG notice2,236 MA residents+7d
  10. SEP 8CA AGCA AG noticeno count stated+7d
  11. SEP 8ME AGME AG noticestates nationwide total 103,782+7d
  12. SEP 8OR AGOR AG noticestates nationwide total 103,782+7d
  13. SEP 9SC AGSC AG notice1,388 SC residents+8d
  14. SEP 9TX AGTX AG noticemost recent · states nationwide total 103,782+8d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 12, 2024
IA AG
Discovered
Dec 20, 2024· 8d undetected
IL AG + IA AG + MT AG +9
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + IA AG + NE AG +9
Attack vector
Unauthorized Access
IA 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)

103,782

Sum of filed state slices

29,883· 28.8% of stated

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

US103,782
TX16,531
WA3,170
IN2,366
MA2,236
SC1,388
NE1,230
NH1,164
ME973
IA616
MT209

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

8 days

Cadence

~1 / 0.6d

vs. multi-state median

1.0× faster

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.