DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed13 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 13 filings

Slim CD Inc. — August 2023 breach

Clustered 13 filings across 12 jurisdictions · filing window Sep 1, 2024 → Oct 16, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

12

Affected · reported

1,693,000

First → last filing

Sep 1, 2024 → Oct 16, 2024

Merge confidence

100%

incident inc_2bd2f48456644acd · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. The filings describe unauthorized access. Intrusion Aug 17, 2023–Jun 15, 2024, discovered Jun 14, 2024 — the first regulatory filing landed 79 days later (flagged late). 1,693,000 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Authentication, and 2 more. Notifications rolled out on a 45-day schedule across 13 filings beginning Sep 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
79days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Filing span
45days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 86dMaine✗ ME AG >90d · 116dWashington⏱ WA AG >30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentials

Incident timeline

Aug 17, 2023breach begins
Jun 14, 2024discovered · members disagree
notification delay · 79 days
Sep 1, 2024first filing
Oct 16, 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 1IL AGIL AG noticefirst filing · no count statedday 0
  2. SEP 5VT AGVT AG noticeno count stated+4d
  3. SEP 6DE AGDE AG noticestates nationwide total 1,693,000+5d
  4. SEP 6MA AGMA AG notice4,087 MA residents+5d
  5. SEP 6OR AGOR AG noticestates nationwide total 1,693,000+5d
  6. SEP 6IN AGIN AG noticestates nationwide total 1,693,000+5d
  7. SEP 6CA AGCA AG noticeno count stated+5d
  8. SEP 6MT AGMT AG notice393 MT residents+5d
  9. SEP 6WA AGWA AG notice2,829 WA residents+5d
  10. SEP 9NH AGNH AG noticeno count stated+8d
  11. SEP 9SC AGSC AG notice3,396 SC residents+8d
  12. OCT 9ME AGME AG noticestates nationwide total 1,693,000+38d
  13. OCT 16ME AGME AG noticemost recent · states nationwide total 1,693,000+45d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 17, 2023 – Jun 15, 2024
VT AG
Discovered
Jun 14, 2024IL AGJun 15, 2024VT AG + DE AG + CA AG +5filings disagree on discovery
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · PCI
VT AG + CA AG + MT AG +6
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)

1,693,000

Sum of filed state slices

16,263· 1.0% of stated

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

US1,693,000
MA4,087
IN3,913
SC3,396
WA2,829
DE848
ME797
MT393

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

45 days

Cadence

~1 / 3.8d

vs. multi-state median

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