This record tracks a ransomware attack claimed by the
ShadowByt3$ group against
StarBucks Company. It collects the publicly disclosed attack details — sector, location and
timeline — as published on the operator's leak site and indexed by Breach House.
Window Zero
EXPOSURE GAP
Window Zero is the time the breach stayed in the open before
anyone said so — the gap between when the attack was first discovered
on the operator's leak site (t1) and when it was publicly disclosed (t2).
The wider this window, the longer victims, staff and customers were exposed with no warning.
153days open
t1 · Published
t2 · Pending
Business Category
Hospitality / Food & Beverage / Tourism
Disclosed / Notified
Not disclosed yet
Attack Summary
StarBucks Failed to reach out to us and didn't pay even $500,000 when we know they can afford it. It's not even that much we were asking for. Since you didn't contact is no negotiations and this is now in the hands of cybercriminals. This is a warning to all companies if you see yourself posted here to reach us. This is the only ammount we have on are servers due to migrating dmca and ignore abuse infrastructure. They were breached on 04/01/2026 and they know they were breached because they closed the s3 bucket starbucks-prod.
Leak Screenshots
SAMPLE
Proof-of-breach screenshots the operator posted from the stolen data. Previews are
redacted and locked — the originals are available on HaveIBeenRansom.
Dark Web Exposure
Findings for starbucks.com
— indexed by HaveIBeenRansom.
28,905
found in Infostealer logs
2,968+
found in Traditional breaches
32+
found in Ransomware leaks
limeleads_breach.7z
TheUnderground - Reborn · breach
••• emails
VerificationsIO_BF.7z.011
Kedr | Forum · breach
••• emails
Apollo.io DB 816millions.rar
Database World ROC · breach
••• emails
@BreachedData1 LinkedIn 2021-23 Cleaned.7z.001
Database World ROC · breach
••• emails
pureincubation-com.7z.001
Database World ROC · breach
••• emails
B F R e p o V 3 F i l e s · breach
••• emails
Database World ROC · breach
••• emails
+ 17 more leak sources locked
Leak volumes are locked
Sign in to reveal how many records each source exposed and the remaining 20 sources.
Legal Disclaimer:
This ransomware victim record reflects information published on the operator's leak site.
Breach.house only records what the operators themselves publish in the
open. We take screenshots of their public pages and keep the proof
material they post there, so that a listing can be verified and its status
tracked over time. We do not purchase data, we do not solicit or encourage
its publication, we do not access any private system, and we do not alter
anything we record. Nothing is offered for download here, and detailed
content is not published on this page or anywhere else on the public site:
access to it is restricted to vetted customers under contract, for
incident response, due diligence and cyber-resilience work.
Breach.house is not affiliated with, and does not act on behalf of, the
operators who publish this material. If you represent an organisation or
individual named here and want a record reviewed or removed, contact us
and we will act on it.