DisclosureLens
Leak SitePressState AGConfirmed8 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedalphvcritical sensitivity
Merged incident · 8 records

The Law Foundation of Silicon Valley — February 2023 breach

Clustered 8 records across 6 jurisdictions: 6 filings, 1 press report and 1 leak-site claim · filing window Jul 6, 2023 → Jul 24, 2023. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

8 records

States

6

Affected · reported

42,525

First → last filing

Jul 6, 2023 → Jul 24, 2023

Merge confidence

100%

incident inc_455d2e1a801e4587 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings, 1 press report and 1 unverified claim. Intrusion Feb 18, 2023, discovered Feb 18, 2023 — the first regulatory filing landed 138 days later. 42,525 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 1 more. Notifications rolled out on a 18-day schedule across 6 filings beginning Jul 6, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
138days

Discovered → first regulatory filing

Discovery variance
103days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 20d

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
18days

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

Sensitive data

identity_governmentminor

Incident timeline

Feb 18, 2023breach begins
Feb 18, 2023discovered · members disagree
notification delay · 138 days
Jul 6, 2023first filing
Jul 24, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

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

  1. MAR 6Leak sitealphv postfirst record · attacker claim · unverifiedday 0
  2. JUL 6ME AGME AG noticestates nationwide total 42,525+122d
  3. JUL 6CA AGCA AG noticeno count stated+122d
  4. JUL 6MT AGMT AG notice9 MT residents+122d
  5. JUL 6IN AGIN AG noticestates nationwide total 42,525+122d
  6. JUL 10NH AGNH AG notice3 NH residents+126d
  7. JUL 24MA AGMA AG noticemost recent · 19 MA residents+140d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 18, 2023
ME AG
Discovered
Feb 18, 2023MT AG + NH AGJun 1, 2023ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · Minor · PII
ME AG + MA AG + CA AG +2
Attack vector
Ransomware
ME 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)

42,525

Sum of filed state slices

44· 0.1% of stated

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

US42,525
MA19
IN12
MT9
NH3
ME1

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

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing6 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 9, 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

18 days

Cadence

~1 / 3.6d

vs. multi-state median

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