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

Running Warehouse LLC — October 2021 breach

Clustered 11 filings across 10 jurisdictions · filing window Dec 16, 2021 → Apr 12, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

1,813,224

First → last filing

Dec 16, 2021 → Apr 12, 2022

Merge confidence

100%

incident inc_cca65bacb3fe4846 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Oct 1, 2021–Oct 15, 2021, discovered Oct 15, 2021 — the first regulatory filing landed 62 days later (flagged late). 1,813,224 individuals reported across the linked filings. Data reported: Financial account, Financial credentials, Identity (basic), and 4 more. Notifications rolled out on a 117-day schedule across 11 filings beginning Dec 16, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
62days

Discovered → first regulatory filing

Discovery variance
45days

Range of discovered_at dates across filings

Filing span
117days

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 clocksCalifornia✗ CA 60-day late · 62dWashington⏱ WA AG >30dMaine✓ ME AG ≤30d · 17dSouth Carolina✓ SC CRA notice dueOregon✓ OR AG ≤45dHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentials

Incident timeline

Oct 1, 2021breach begins
Oct 15, 2021discovered · members disagree
notification delay · 62 days
Dec 16, 2021first filing
Apr 12, 2022most 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. DEC 16ME AGME AG noticefirst filing · states nationwide total 1,813,224day 0
  2. DEC 16DE AGDE AG noticeno count statedday 0
  3. DEC 16SC AGSC AG notice7,461 SC residentsday 0
  4. DEC 16IN AGIN AG noticestates nationwide total 1,813,224day 0
  5. DEC 16OR AGOR AG noticestates nationwide total 1,813,224day 0
  6. DEC 16HI AGHI AG notice1,071 HI residentsday 0
  7. DEC 16MT AGMT AG notice2,214 MT residentsday 0
  8. DEC 17WA AGWA AG notice17,556 WA residents+1d
  9. DEC 18CA AGCA AG noticeno count stated+2d
  10. DEC 18MA AGMA AG notice15,306 MA residents+2d
  11. APR 12CA AGCA AG noticemost recent · no count stated+117d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 1, 2021
ME AG
Discovered
Oct 15, 2021DE AG + SC AG + HI AG +3Nov 29, 2021ME AG + OR AGfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Financial credentials · Identity (basic) · PCI · PII
ME AG + DE AG + SC AG +5
Attack vector
Unauthorized Access
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)

1,813,224

Sum of filed state slices

56,941· 3.1% of stated

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

US1,813,224
WA17,556
MA15,306
IN10,539
SC7,461
ME2,794
MT2,214
HI1,071

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

117 days

Cadence

~1 / 11.7d

vs. multi-state median

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