889 employees
Starbucks Corporation has disclosed a data breach that compromised the sensitive personal and financial information of 889 of its employees (referred to as "partners"). The incident resulted from a phishing campaign that successfully harvested credentials for the company's internal "Partner Central" portal. The unauthorized access took place between January 19 and February 11, 2026. After discovering the suspicious activity on February 6, Starbucks, with the help of external experts, eradicated the threat from its systems. The compromised data includes Social Security numbers and bank account details. The company has emphasized that the breach was contained to the employee portal and did not impact any customer information. Affected employees are being offered 24 months of complimentary identity protection services.
The attack was a classic credential phishing campaign. Threat actors created websites that convincingly impersonated the legitimate Starbucks "Partner Central" login page. Phishing emails were then sent to Starbucks employees, luring them to these fake sites where they were prompted to enter their login credentials. Once the attackers harvested a valid username and password, they used them to log into the real portal and access the employee's personal information.
The extended duration of access, from January 19 to February 11, suggests that the attackers may have been accessing accounts intermittently to avoid detection, or that the company's monitoring systems did not immediately flag the anomalous logins.
The attack chain followed a standard phishing-to-breach methodology:
T1566.002 - Spearphishing Link).T1598.003 - Spearphishing via Service).T1078 - Valid Accounts).While the number of affected individuals (889) is relatively small compared to other major breaches, the impact on those employees is severe. The exposure of Social Security numbers combined with financial account and routing numbers puts them at extremely high risk for:
For Starbucks, the incident is a blow to its internal security posture and trust with its employees. While no customer data was involved, the breach of sensitive employee data still carries reputational risk and the direct costs of the investigation, remediation, and identity protection services.
Starbucks detected suspicious activity on February 6, nearly three weeks after the unauthorized access began. This indicates a potential delay in detecting the anomalous logins. Once detected, the company engaged external experts and reports that it took five days to fully contain the incident and remove the attackers' access. The company has notified law enforcement and is providing identity protection services through Experian to the affected employees.
New details reveal the Starbucks data breach was a supply chain attack, compromising a third-party vendor's access to Partner Central, not direct employee phishing.
Starbucks filed breach notification with Maine AG, confirming exposure of employee dates of birth in addition to previously reported data.
Implementing MFA on the 'Partner Central' portal would have prevented the attackers from using the stolen credentials.
Mapped D3FEND Techniques:
Training employees to recognize and report phishing emails is a critical layer of defense.
Use email and web filtering to block access to known phishing sites and newly registered domains.
Mapped D3FEND Techniques:
Unauthorized access to employee accounts begins.
Starbucks becomes aware of suspicious activity.
Unauthorized access is fully contained.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.