Carolina Foods
bd_92b7ea5855ba1e9f · schema v1 · pii pii-v1
Full breach record for Carolina Foods →2 incidents on fileThreat-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
CAROLINA FOODS INC., creator of one of America’s first honey buns and the Duchess brand, is a sweet goods bakery located in Charlotte, North Carolina. For decades, our customers have enjoyed our honey buns, donuts, pastries and pies. Our products bring families together for breakfast, snacks, and on holidays and special occasions. At Carolina Foods, we make all of our products using the finest ingredients, blended in house to ensure that we have superior taste and quality. Once you taste our treats you will come back wanting more. Product quality is our number one priority, and we go to great lengths to ensure that our products are recognized as the “best in class” in their respective categories. Every day we strive to create a product that is loved by many. Quality, taste, and value bring our customers back for more. Honey buns are one of our many specialties, and while there are many brands on the market today, we challenge you to find one that tastes better than ours. Once you bite into a delicious, melt in your mouth Duchess honey bun, you will never buy another brand.SITE: www.carolinafoodsinc.com Address : 1807 SOUTH TRYON STREET CHARLOTTE, NC 28203 USAALL DATA SIZE: ~450gb 1. All data company 2. Users personal data 3. Accounting & etc...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 12, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- New Hampshire State AGbd_a61f60faaf9be14a2024-06-17 · +97dVerified by operator
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Mar 12, last Jun 17 (NH) — a 97-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.