DisclosureLens
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 6 filings

COLUMBIA GRAIN INTERNATIONAL, LLC — March 2022 breach

Clustered 6 filings across 5 jurisdictions · filing window Jul 19, 2022 Nov 23, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

3,710

First → last filing

Jul 19, 2022 Nov 23, 2022

Merge confidence

100%

incident inc_6d7eebb8e93e4bc2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 15, 2022–Mar 21, 2022, discovered Mar 21, 2022 — the first regulatory filing landed 246 days later (flagged late). 3,710 individuals reported across the linked filings. Data reported: Financial account, Financial credentials, and Identity (basic). Notifications rolled out on a 127-day schedule across 5 filings beginning Jul 19, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
246days

Discovered → first regulatory filing

Discovery variance
147days

Range of discovered_at dates across filings

Leak precedence
126days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
127days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >90d · 99dOregon OR AG >45dLeak gap Leak >90dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Mar 15, 2022breach begins
Mar 21, 2022discovered · members disagree
notification delay · 246 days
Nov 22, 2022first filing
Nov 23, 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. JUL 19Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. NOV 22ME AGME AG noticestates nationwide total 3,710+126d
  3. NOV 23MT AGMT AG notice1,496 MT residents+127d
  4. NOV 23OR AGOR AG noticestates nationwide total 3,710+127d
  5. NOV 23ME AGME AG noticestates nationwide total 3,710+127d
  6. NOV 23IN AGIN AG noticemost recent · states nationwide total 3,710+127d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 21, 2022
ME AG
Discovered
Mar 21, 2022MT AGAug 15, 2022ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic)
ME AG + MT AG
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)

3,710

Sum of filed state slices

1,498· 40.4% of stated

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

US3,710
MT1,496
ME1
IN1

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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 Aug 22, 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

127 days

Cadence

~1 / 25.4d

vs. multi-state median

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