DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedsnatchhigh sensitivity
Merged incident · 6 filings

Wasserstrom Holdings, Inc. — April 2023 breach

Clustered 6 filings across 5 jurisdictions · filing window Jun 9, 2023 → Jul 20, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

10,520

First → last filing

Jun 9, 2023 → Jul 20, 2023

Merge confidence

100%

incident inc_81a00beaf8e24586 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Apr 20, 2023–Apr 21, 2023, discovered Apr 21, 2023 — the first regulatory filing landed 49 days later. 10,520 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 41-day schedule across 4 filings beginning Jun 9, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
49days

Discovered → first regulatory filing

Discovery variance
20days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 39d

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

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 · 68dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 20, 2023breach begins
Apr 21, 2023discovered · members disagree
notification delay · 49 days
Jun 9, 2023first filing
Jul 18, 2023most 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. JUN 9IN AGIN AG noticefirst filing · states nationwide total 10,520day 0
  2. JUN 9MA AGMA AG notice12 MA residentsday 0
  3. JUL 18Leak sitesnatch postattacker claim · unverified+39d
  4. JUL 18MT AGMT AG notice1 MT residents+39d
  5. JUL 18ME AGME AG noticestates nationwide total 10,520+39d
  6. JUL 20Leak sitecactus postmost recent · attacker claim · unverified+41d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 20, 2023
IN AG
Discovered
Apr 21, 2023MT AGMay 11, 2023ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
MA AG + MT AG + ME AG
Attack vector
Unauthorized Access
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)

10,520

Sum of filed state slices

29· 0.3% of stated

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

US10,520
IN13
MA12
ME3
MT1

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 filing4 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 Aug 22, 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

41 days

Cadence

~1 / 8.2d

vs. multi-state median

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