Peter Pan Seafoods, Inc.
ent_f8848b085627adb430ca2449
Disclosures
5
State AG · 5 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
8,846
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Peter Pan Seafoods, Inc.
- Normalized
- peter pan seafoods— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (5)newest first
- 🦬Montana State AGas victim2021-01-11
Peter Pan Seafoods, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-01-11. The breach occurred on 12/12/2020. 75 Montana residents were affected.
- 🦞Maine State AGas victim2021-01-04
Peter Pan Seafoods, Inc. reported a ransomware incident that occurred and was discovered on December 12, 2020. The breach affected 8 Maine residents, compromising their names and Social Security numbers. The company provided written notification to the affected individuals on January 11, 2021, and offered two years of identity theft protection services through Experian IdentityWorks.
- 🐻California State AGas victim2021-01-04
Peter Pan Seafoods, Inc. experienced a ransomware attack on December 12, 2020, where an attacker encrypted systems to extort money. The incident affected current and former employees, exposing names, addresses, Social Security numbers, and dates of birth. The company engaged third-party forensics, upgraded systems, and offered two years of identity monitoring.
- 🦫Oregon State AGas victim2021-01-04
Peter Pan Seafoods, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2021-01-04. The breach occurred during 12/12/2020 - 12/13/2020. The breach was discovered on 12/12/2020. 8,846 individuals were affected. Notice was sent on 1/4/2021.
- 🌲Washington State AGas victim2021-01-04
Peter Pan Seafoods, Inc., a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2020-12-12 and filed notice on 2021-01-04. 1,661 Washington residents were affected. 23 days elapsed between awareness and notification. 0 days to identify the breach. 14 days to contain the breach.