DisclosureLens
GLOBALMalwareAgriculture & FoodAgricultureRansomwareBlack BastaRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

Carolina Foods

bd_92b7ea5855ba1e9f · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Mar 12, 2024

To disclose

—

Affected

Not disclosed

Linked

3 records

Confidence

50%
Full breach record for Carolina Foods →

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.

Group activity: Agriculture and Food ProductionDiscovered: 2024-03-27

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

Incident timeline — mostly unverified

? — ?

Breach window unknown

Mar 12, 2024

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

This leak-site claim is one of 3 records about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Filing propagation · 2 filings · 2 states

View merged incident ↗

Pattern: first filing Jun 7 (IN), last Jun 17 (NH) — a 10-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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.