Bridgford Foods Corporation
ent_1d9ec4f69f5787a35af8b97a
Disclosures
5
State AG · 5 jurisdictions
Multi-filing incidents
1
incidents joining 2+ filings here
Max affected reported
1,377
nationwide · State AG ME
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Bridgford Foods Corporation
- Normalized
- bridgford foods— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- 0000014177
- Domain
- None on record
Disclosure history (5)newest first
- New Hampshire State AGas victim2020-10-26
Bridgford Foods Corporation notified the NH Attorney General of unauthorized access to servers in a third-party hosted environment on July 25, 2020. The incident affected 3 New Hampshire residents, exposing names, addresses, and Social Security numbers. The investigation is ongoing. Bridgford engaged forensic specialists and is offering 12 months of credit monitoring.
- Maine State AGas victim2020-10-22
Bridgford Foods Corporation reported a data breach affecting 1,377 individuals due to an incident at a third-party vendor. The breach occurred on July 25, 2020, and was discovered on September 14, 2020. The compromised information includes names and Social Security numbers. Affected individuals were notified on October 22, 2020, and offered 12 months of credit monitoring services through Experian.
- Indiana State AGas victim2020-10-22
Bridgeford Foods Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2020-07-25 and was reported on 2020-10-22. 19 Indiana residents were affected. 1,377 individuals affected in total.
- Massachusetts State AGas victim2020-10-22
Bridgford Foods Corporation reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2020-10-22. 8 Massachusetts residents were affected. The report records the breach type as electronic.
- Montana State AGas victim2020-10-22
Bridgford Foods Corporation notified individuals of unauthorized access to servers in a third-party hosted environment on July 25, 2020. The incident exposed names, SSNs, addresses, and DOBs. The company engaged forensic specialists and offered 12 months of credit monitoring. Notices were sent in October 2020.