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

BOB'S RED MILL NATURAL FOODS, INC. — November 2021 breach

Clustered 15 filings across 6 jurisdictions · filing window Dec 23, 2021 → Apr 22, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

6

Affected · reported

4,467

First → last filing

Dec 23, 2021 → Apr 22, 2022

Merge confidence

100%

incident inc_d849f41a9d194edb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. Intrusion Nov 28, 2021–Mar 1, 2022, discovered Nov 28, 2021 — the first regulatory filing landed 25 days later. 4,467 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 120-day schedule across 15 filings beginning Dec 23, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
25days

Discovered → first regulatory filing

Discovery variance
114days

Range of discovered_at dates across filings

Filing span
120days

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 · 6dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Nov 28, 2021breach begins
Nov 28, 2021discovered · members disagree
notification delay · 25 days
Dec 23, 2021first filing
Apr 22, 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 23ME AGME AG noticefirst filing · states nationwide total 2,585day 0
  2. JAN 4MA AGMA AG notice16 MA residents+12d
  3. JAN 4OR AGOR AG noticestates nationwide total 2,585+12d
  4. JAN 4ME AGME AG noticestates nationwide total 2,585+12d
  5. JAN 6ME AGME AG noticestates nationwide total 4,325+14d
  6. JAN 7NH AGNH AG notice1 NH residents+15d
  7. JAN 18IN AGIN AG noticestates nationwide total 4,467+26d
  8. JAN 19ME AGME AG noticestates nationwide total 4,325+27d
  9. JAN 24NH AGNH AG notice2 NH residents+32d
  10. APR 12ME AGME AG noticestates nationwide total 1,866+110d
  11. APR 15MT AGMT AG notice8 MT residents+113d
  12. APR 15ME AGME AG noticestates nationwide total 1,866+113d
  13. APR 15NH AGNH AG notice12 NH residents+113d
  14. APR 20MA AGMA AG notice62 MA residents+118d
  15. APR 22IN AGIN AG noticemost recent · states nationwide total 1,866+120d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 1, 2021
ME AG
Discovered
Nov 28, 2021NH AGDec 17, 2021ME AG + OR AGMar 1, 2022MT AGMar 22, 2022ME AG + NH AGfilings disagree on discovery
Data types
Financial · Financial account · Financial credentials · Identity (basic) · Government ID · PCI · PII
ME AG + NH AG + MT AG +1
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)

4,467

Sum of filed state slices

110· 2.5% of stated

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

US4,467
MA62
IN17
NH12
ME11
MT8

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

120 days

Cadence

~1 / 8.6d

vs. multi-state median

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