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

Simmons Perrine Moyer Bergman PLC — May 2023 breach

Clustered 5 filings across 5 jurisdictions · filing window Sep 5, 2023 → May 13, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

2,391

First → last filing

Sep 5, 2023 → May 13, 2024

Merge confidence

100%

incident inc_c9a7eeb1475f44f7 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 11, 2023–Jul 3, 2023, discovered Jul 3, 2023 — the first regulatory filing landed 312 days later (flagged late). 2,391 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), IP / system, and 1 more. Notifications rolled out on a 251-day schedule across 4 filings beginning Sep 5, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
312days

Discovered → first regulatory filing

Discovery variance
266days

Range of discovered_at dates across filings

Leak precedence
248days 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
251days

Time between earliest and latest filing

Not recorded for this incident

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

May 11, 2023breach begins
Jul 3, 2023discovered · members disagree
notification delay · 312 days
May 10, 2024first filing
May 13, 2024most 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 5Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. MAY 10IN AGIN AG noticestates nationwide total 2,391+248d
  3. MAY 10VT AGVT AG notice2 VT residents+248d
  4. MAY 13MA AGMA AG notice2 MA residents+251d
  5. MAY 13ME AGME AG noticemost recent · states nationwide total 2,391+251d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 11, 2023
IN AG
Discovered
Jul 3, 2023VT AGMar 25, 2024ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · IP / system
VT AG + ME AG + MA AG
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)

2,391

Sum of filed state slices

19· 0.8% of stated

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

US2,391
IN11
ME4
VT2
MA2

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

251 days

Cadence

~1 / 62.8d

vs. multi-state median

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