DisclosureLens
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcednitrogenhigh sensitivity
Merged incident · 6 filings

QualiChem Metalworking — October 2025 breach

Clustered 6 filings across 5 jurisdictions · filing window Jan 27, 2026 Apr 29, 2026. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

644

First → last filing

Jan 27, 2026 Apr 29, 2026

Merge confidence

100%

incident inc_ced6ec3031894ce1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Oct 23, 2025–Dec 16, 2025, discovered Dec 16, 2025 — the first regulatory filing landed 84 days later (flagged late). 644 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 91-day schedule across 5 filings beginning Jan 27, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
84days

Discovered → first regulatory filing

Discovery variance
71days

Range of discovered_at dates across filings

Leak precedence
41days 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
91days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >90d · 134dLeak gap Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 23, 2025breach begins
Dec 16, 2025discovered · members disagree
notification delay · 84 days
Mar 10, 2026first filing
Apr 29, 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. JAN 27Leak sitenitrogen postfirst filing · attacker claim · unverifiedday 0
  2. MAR 10NH AGNH AG notice1 NH residents+41d
  3. MAR 10IN AGIN AG noticestates nationwide total 644+41d
  4. APR 29MA AGMA AG notice6 MA residents+91d
  5. APR 29ME AGME AG noticestates nationwide total 644+91d
  6. APR 29NH AGNH AG noticemost recent · 2 NH residents+91d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 23, 2025Dec 16, 2025
NH AG
Discovered
Dec 16, 2025ME AG + NH AGFeb 25, 2026NH AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
NH AG + MA AG + ME AG
Attack vector
Unauthorized Access
NH 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)

644

Sum of filed state slices

38· 5.9% of stated

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

US644
IN26
MA6
ME4
NH2

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

91 days

Cadence

~1 / 18.2d

vs. multi-state median

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