starbucks-sdknpm
starbucks-sdk is a confirmed malicious npm package (MAL-2026-16345) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in starbucks-sdk (npm)
What this malware does
The package's package.json declares a preinstall script that runs callback.js on npm install. callback.js collects os.hostname(), os.userInfo(), os.platform(), the current working directory, and a timestamp, then enumerates process.env and selects keys matching /token|secret|key|pass|auth|api|aws/i (up to 10 entries). The collected data is POSTed via https.request to https://api.telegram.org/bot<BOT_TOKEN>/sendMessage using a hardcoded Telegram bot token and chat_id (bot 8636277735, chat_id 1064260758). The name mimics a legitimate vendor SDK but the package's only behavior is install-time reconnaissance and exfiltration of installer/build-host identity and credential-shaped environment variable names to an attacker-controlled Telegram channel — a dependency-confusion recon payload.
The OpenSSF Package Analysis project identified 'starbucks-sdk' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for starbucks-sdk (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging starbucks-sdk across your stack and pipelines.
If you installed it — respond
starbucks-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If starbucks-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks starbucks-sdk before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks starbucks-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.