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

S.V.D.P. Management Inc. — September 2024 breach

Clustered 11 filings across 11 jurisdictions · filing window Aug 27, 2025 → Sep 4, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

95,329

First → last filing

Aug 27, 2025 → Sep 4, 2025

Merge confidence

100%

incident inc_3d8bcfac687c4be4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Sep 26, 2024–Oct 12, 2024, discovered Jul 29, 2025 — the first regulatory filing landed 29 days later. 95,329 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 8-day schedule across 11 filings beginning Aug 27, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
29days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
8days

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 >14 bdayMaine⏱ ME AG >30d · 31dWashington⏱ WA AG >30dOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 31dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 26, 2024breach begins
Jul 29, 2025discovered
notification delay · 29 days
Aug 27, 2025first filing
Sep 4, 2025most 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. AUG 27MT AGMT AG noticefirst filing · 37 MT residentsday 0
  2. AUG 29IN AGIN AG noticestates nationwide total 95,329+2d
  3. AUG 29OR AGOR AG noticestates nationwide total 95,329+2d
  4. AUG 29CA AGCA AG noticeno count stated+2d
  5. AUG 29VT AGVT AG noticeno count stated+2d
  6. AUG 29ME AGME AG notice18 ME residents+2d
  7. AUG 29NH AGNH AG notice11 NH residents+2d
  8. AUG 29WA AGWA AG notice3,893 WA residents+2d
  9. AUG 29MA AGMA AG notice68 MA residents+2d
  10. AUG 29NE AGNE AG notice32 NE residents+2d
  11. SEP 4TX AGTX AG noticemost recent · states nationwide total 95,329+8d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 26, 2024 – Oct 12, 2024
MT AG
Discovered
Jul 29, 2025· 306d undetected
MT AG + OR AG + CA AG +6
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + CA AG + VT AG +6
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)

95,329

Sum of filed state slices

4,531· 4.8% of stated

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

US95,329
WA3,893
TX412
MA68
IN60
MT37
NE32
ME18
NH11

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

8 days

Cadence

~1 / 0.8d

vs. multi-state median

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