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

OBI Seafoods, LLC — August 2024 breach

Clustered 11 filings across 11 jurisdictions · filing window Mar 12, 2025 → Mar 20, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

19,014

First → last dated filing

Mar 12, 2025 → Mar 20, 2025

Merge confidence

100%

incident inc_058044a095504be4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Aug 12, 2024–Aug 16, 2024, discovered Aug 16, 2024 — the first regulatory filing landed 208 days later; 4 later filings were flagged late. 19,014 individuals reported across the linked filings. Data reported: Government ID, Biometric, Identity (basic), and 4 more. Notifications rolled out on a 8-day schedule across 10 dated filings beginning Mar 12, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
208days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
8days

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 clocksMaryland✗ MD AG >90dOregon✗ OR AG >45dWashington✗ WA AG >90dVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 215dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

Aug 12, 2024breach begins
Aug 16, 2024discovered
notification delay · 208 days
Mar 12, 2025first dated filing
Mar 20, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. MAR 12NE AGNE AG noticefiling day not on record · no count stated—
  2. MAR 12IN AGIN AG noticefirst filing · states nationwide total 19,014day 0
  3. MAR 19CA AGCA AG noticeno count stated+7d
  4. MAR 19MD AGMD AG notice17 MD residents+7d
  5. MAR 19OR AGOR AG noticestates nationwide total 19,014+7d
  6. MAR 19ME AGME AG noticestates nationwide total 19,014+7d
  7. MAR 19WA AGWA AG notice4,689 WA residents+7d
  8. MAR 19MT AGMT AG notice45 MT residents+7d
  9. MAR 20MA AGMA AG notice9 MA residents+8d
  10. MAR 20NH AGNH AG notice6 NH residents+8d
  11. MAR 20VT AGVT AG noticemost recent · no count stated+8d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 12, 2024
IN AG
Discovered
Aug 16, 2024· 4d undetected
NE AG + CA AG + MD AG +6
Data types
Biometric · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
NE AG + CA AG + MD AG +6
Attack vector
Unauthorized Access
NE 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)

19,014

Sum of filed state slices

4,798· 25.2% of stated

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

US19,014
WA4,689
MT45
IN25
MD17
MA9
ME7
NH6

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

8 days

Cadence

~1 / 0.9d

vs. multi-state median

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