bodega-sdknpm
bodega-sdk is a confirmed malicious npm package (MAL-2026-5801) that steals credentials and exfiltrates sensitive data (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bodega-sdk (npm)
What this malware does
flow/surf-lending DeFi cred-exfil campaign sibling (c1655). preinstall node index.js || true exfils env secrets to raw C2 2.25.140.71:8443/surflending/npm-confusion (verified identical). No-renotify.
package.json declares preinstall: node index.js, which fires automatically on npm install. index.js collects host identifiers (os.hostname(), os.userInfo().username, cwd) and enumerates process.env, filtering keys by the regex /key|seed|secret|token|private|mnemonic|password|blockfrost|redis|telegram|batcher/i to capture credential-shaped values (API keys, seed phrases, mnemonics, private keys, Telegram bot tokens, Blockfrost keys, Redis URLs, batcher keys). The harvested JSON is POSTed to https://2.25.140.71:8443/surflending/npm-confusion — a hardcoded bare-IP endpoint. The attacker-chosen URL path /surflending/npm-confusion and the sentinel version 9.9.9 indicate a dependency-confusion attack targeting a private bodega-sdk package (likely SurfLending/Bodega DEX on Cardano): any organization with an internal package of this name risks the public copy resolving on install, leaking credentials from CI runners and developer machines unconditionally.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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 bodega-sdk (version 9.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bodega-sdk across your stack and pipelines.
If you installed it — respond
bodega-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 bodega-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 bodega-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
- SafeDep · finder
Detect & block this
O3 blocks bodega-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.