Lagunitas
bd_7f9d0e76fee05991 · schema v1 · pii pii-v1
Full breach record for Lagunitas →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
The Lagunitas Brewing Company began on a kitchen stove in Northern California in 1993 and has been crafting hop-forward beers ever since. Welcoming the open-minded with open taps and simple truths: Beer Speaks (for itself), Life Is Uncertain (don’t sip), and It’s Good To Have Friends. To quote our BrewMonster, “Lagunitas is made up of all kinds and creeds; punk rockers, misfits, ivy leaguers, weirdos, Waldos, Sparkle Ponies, Musicians, and everything in between ... Just a pack of stray dogs that found—despite our vast and wild differences—that the love and respect for the freedom to be different is what brought us together and made it all work.” Whether we’re supporting local communities by turning beer into money for the cause, or simply fueling stories and songs with IPA and other creations—we always have a spot for you at our bar. Come as you are. And bring your dog, too. Here’s how it all really happened, or at least how we remember it. Heck... we don’t remember a lot, so this is at least how we thought it might have gone or something...SITE: www.lagunitas.com Address : 1280 N. McDowell Boulevard Petaluma, Calif. 94954 USAALL DATA SIZE: ~700gb 1. All data company 2. Users personal data & etc...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 12, 2024
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
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.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
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.