Peco Foods Inc.
bd_9389970dbade6326 · schema v1 · pii pii-v1
Full breach record for Peco Foods Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Black Basta on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Peco Foods hopes you’ll pick up their poultry. Producing some 24 million pounds of poultry each week, the company processes private-label and store-brand chicken for US retail and foodservice customers. Peco Foods also exports items to Canada, Mexico, South America, Asia, and Eastern Europe. The processing company’s frozen, deli, and tray-pack products include boneless, skinless chicken breasts and tenderloins; boneless thighs; and jumbo legs and wings; as well as value-added breaded and flavored products. As a fully integrated processor, Peco Foods operates feed mills and hatcheries in three US states to support its poultry production facilities. Peco Foods is owned and operated by the founding Hickman family.SITE: www.pecofoods.com Address : 1101 Greensboro Ave Tuscaloosa, Alabama 35401, United StatesALL DATA SIZE: 510gb 1. Users personal documents 2. Human Resources 3. Accounting 4. Scans and etc...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 19, 2023
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- Vermont State AGbd_30952e393af498ca2024-07-24 · +217dVerified
- Indiana State AGbd_f7824e3140fe5c242024-07-24 · +217dVerified
- Montana State AGbd_7c18d4393a55845d2024-07-25 · +218dVerified by operator
- Maine State AGbd_e535a9329c5c160c2024-07-25 · +218dVerified by operator
Filing propagation · 4 filings · 4 states
View merged incident ↗Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.