DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed10 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 10 records

STOCK Development — April 2023 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filing window Jan 24, 2025 → Feb 4, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

13,147

First → last dated filing

Jan 24, 2025 → Feb 4, 2025

Merge confidence

100%

incident inc_4bca5365724e4642 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Apr 25, 2023–Mar 2, 2024, discovered Apr 25, 2023. 13,147 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 11-day schedule across 6 dated filings beginning Jan 24, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
545days

Range of discovered_at dates across filings

Filing span
11days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 25, 2023breach begins
Apr 25, 2023discovered · members disagree
Jan 24, 2025first dated filing
Feb 4, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

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

  1. MAR 2Leak sitelockbit_3 postfirst record · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JAN 24MT AGMT AG notice13 MT residents+328d
  4. JAN 24IN AGIN AG noticestates nationwide total 13,147+328d
  5. JAN 24VT AGVT AG noticeno count stated+328d
  6. JAN 24NE AGNE AG noticefiling day not on record · no count stated—
  7. JAN 30NH AGNH AG notice75 NH residents+334d
  8. FEB 3ME AGME AG noticestates nationwide total 13,147+338d
  9. FEB 4MA AGMA AG noticemost recent · 381 MA residents+339d
  10. NOV 13MD AGMD AG noticefiling day not on record · 160 MD residents—
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 25, 2023 – Mar 2, 2024
MT AG
Discovered
Apr 25, 2023IL AGMar 2, 2024MT AG + VT AG + NH AG +1Oct 21, 2024NE AG + ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID
MT AG + VT AG + NH AG +3
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)

13,147

Sum of filed state slices

847· 6.4% of stated

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

US13,147
MA381
IN181
MD160
NH75
ME37
MT13

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

11 days

Cadence

~1 / 2.2d

vs. multi-state median

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