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

Designed Receivable Solutions — January 2024 breach

Clustered 17 filings across 9 jurisdictions · filing window Apr 26, 2024 → Jul 16, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 filings

States

9

Affected · reported

585,204

First → last filing

Apr 26, 2024 → Jul 16, 2024

Merge confidence

100%

incident inc_1ad93ba63d354cd8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 17 regulatory filings. Intrusion Jan 8, 2024–Jan 18, 2024, discovered Jan 22, 2024 — the first regulatory filing landed 95 days later (flagged late). 585,204 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 81-day schedule across 17 filings beginning Apr 26, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
95days

Discovered → first regulatory filing

Discovery variance
51days

Range of discovered_at dates across filings

Filing span
81days

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 bdayWashington✗ WA AG >90dMaine✗ ME AG >90d · 156dCalifornia✗ CA 60-day late · 151dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 8, 2024breach begins
Jan 22, 2024discovered · members disagree
notification delay · 95 days
Apr 26, 2024first filing
Jul 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. APR 26IN AGIN AG noticefirst filing · states nationwide total 585,035day 0
  2. APR 26VT AGVT AG noticeno count statedday 0
  3. APR 26OR AGOR AG noticestates nationwide total 498,686day 0
  4. APR 26MT AGMT AG notice290 MT residentsday 0
  5. APR 26NH AGNH AG notice36 NH residentsday 0
  6. APR 26CA AGCA AG noticeno count statedday 0
  7. APR 26WA AGWA AG notice1,131 WA residentsday 0
  8. APR 27MA AGMA AG notice362 MA residents+1d
  9. APR 27ME AGME AG noticestates nationwide total 498,686+1d
  10. JUN 21VT AGVT AG noticeno count stated+56d
  11. JUN 26CA AGCA AG noticeno count stated+61d
  12. JUN 26NH AGNH AG noticeno count stated+61d
  13. JUN 26ME AGME AG noticestates nationwide total 585,204+61d
  14. JUL 16NH AGNH AG noticeno count stated+81d
  15. JUL 16VT AGVT AG noticeno count stated+81d
  16. JUL 16ME AGME AG noticestates nationwide total 585,035+81d
  17. JUL 16CA AGCA AG noticemost recent · no count stated+81d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 8, 2024
IN AG
Discovered
Jan 22, 2024VT AG + MT AG + NH AG +3Mar 13, 2024OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + MT AG + NH AG +4
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)

585,204

Sum of filed state slices

2,272· 0.4% of stated

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

US585,204
WA1,131
IN364
MA362
MT290
ME89
NH36

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

81 days

Cadence

~1 / 5.1d

vs. multi-state median

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