DisclosureLens
State AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

SLT Lending SPV, Inc. — March 2023 breach

Clustered 8 filings across 8 jurisdictions · filed May 24, 2023. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

40,646

First → last filing

May 24, 2023

Merge confidence

100%

incident inc_136fd6a7036546b2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Mar 15, 2023–Mar 25, 2023, discovered Mar 25, 2023 — the first regulatory filing landed 60 days later. 40,646 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
47days

Range of discovered_at dates across filings

Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington WA AG >30dVermont VT AG ≤14 bdayOregon OR AG ≤45dMaine ME AG ≤30d · 13dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 15, 2023breach begins
Mar 25, 2023discovered · members disagree
notification delay · 60 days
May 24, 2023first filing
watching for filings

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

Member cascade — every filing about this breach

  1. MAY 24WA AGWA AG noticefirst filing · 1,748 WA residentsday 0
  2. MAY 24IN AGIN AG noticestates nationwide total 40,646day 0
  3. MAY 24MA AGMA AG notice808 MA residentsday 0
  4. MAY 24VT AGVT AG noticeno count statedday 0
  5. MAY 24OR AGOR AG noticestates nationwide total 40,646day 0
  6. MAY 24MT AGMT AG notice15 MT residentsday 0
  7. MAY 24CA AGCA AG noticeno count statedday 0
  8. MAY 24ME AGME AG noticemost recent · states nationwide total 40,646day 0
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 15, 2023Mar 25, 2023
WA AG
Discovered
Mar 25, 2023WA AGMay 11, 2023VT AG + OR AG + MT AG +1filings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
WA AG + VT AG + MT AG +3
Attack vector
Ransomware
WA 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)

40,646

Sum of filed state slices

6,798· 16.7% of stated

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

US40,646
IN4,212
WA1,748
MA808
MT15
ME15

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 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 Jun 12, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.