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

CBD Industries, LLC — March 2020 breach

Clustered 8 filings across 8 jurisdictions · filing window Sep 28, 2020 → Oct 2, 2020. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

42,694

First → last filing

Sep 28, 2020 → Oct 2, 2020

Merge confidence

100%

incident inc_2dd3f143df9149b3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion Mar 30, 2020–Apr 19, 2025, discovered Aug 26, 2020 — the first regulatory filing landed 33 days later. 42,694 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
33days

Discovered → first regulatory filing

Discovery variance
146days

Range of discovered_at dates across filings

Filing span
4days

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 clocksMaine⏱ ME AG >30d · 34dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Mar 30, 2020breach begins
Aug 26, 2020discovered · members disagree
notification delay · 33 days
Sep 28, 2020first filing
Oct 2, 2020most 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 28IN AGIN AG noticefirst filing · states nationwide total 42,694day 0
  2. SEP 29NH AGNH AG notice332 NH residents+1d
  3. SEP 29MT AGMT AG notice168 MT residents+1d
  4. SEP 29OR AGOR AG noticestates nationwide total 42,694+1d
  5. SEP 29WA AGWA AG noticestates nationwide total 1,088+1d
  6. SEP 29ME AGME AG noticestates nationwide total 42,694+1d
  7. SEP 29CA AGCA AG noticeno count stated+1d
  8. OCT 2MA AGMA AG noticemost recent · 1,495 MA residents+4d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 30, 2020
IN AG
Discovered
Aug 26, 2020OR AG + ME AGSep 28, 2020NH AGJan 19, 2021WA AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PCI
NH AG + MT AG + WA AG +3
Attack vector
Misconfiguration
NH 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)

42,694

Sum of filed state slices

3,017· 7.1% of stated

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

US42,694
MA1,495
IN782
NH332
ME192
MT168
WA48

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

4 days

Cadence

~1 / 0.6d

vs. multi-state median

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