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

Peter Pan Seafoods, Inc. — December 2020 breach

Clustered 8 filings across 8 jurisdictions · filing window Jan 4, 2021 → Jan 11, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

8,846

First → last filing

Jan 4, 2021 → Jan 11, 2021

Merge confidence

100%

incident inc_cb183e202af94a72 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe a ransomware attack. Intrusion Dec 12, 2020–Dec 26, 2020, discovered Dec 12, 2020 — the first regulatory filing landed 23 days later. 8,846 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Employment. Notifications rolled out on a 7-day schedule across 8 filings beginning Jan 4, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
23days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
7days

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 · 23dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dWashington✓ WA AG ≤30dCalifornia✓ CA 60-day OK · 30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 12, 2020breach begins
Dec 12, 2020discovered
notification delay · 23 days
Jan 4, 2021first filing
Jan 11, 2021most 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. JAN 4ME AGME AG noticefirst filing · states nationwide total 8,846day 0
  2. JAN 4MA AGMA AG notice1 MA residentsday 0
  3. JAN 4OR AGOR AG noticestates nationwide total 8,846day 0
  4. JAN 4WA AGWA AG noticestates nationwide total 8,846day 0
  5. JAN 4CA AGCA AG noticeno count statedday 0
  6. JAN 11NH AGNH AG noticestates nationwide total 8,846+7d
  7. JAN 11MT AGMT AG notice75 MT residents+7d
  8. JAN 11IN AGIN AG noticemost recent · states nationwide total 8,846+7d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 12, 2020
ME AG
Discovered
Dec 12, 2020
ME AG + OR AG + WA AG +3
Data types
Employment · Identity (basic) · Government ID
ME AG + WA AG + CA AG +3
Attack vector
Ransomware
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)

8,846

Sum of filed state slices

1,769· 20.0% of stated

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

US8,846
WA1,661
MT75
IN22
ME8
NH2
MA1

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

7 days

Cadence

~1 / 1d

vs. multi-state median

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