zomato-mcpnpm
Malicious code in zomato-mcp (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
On npm install, the package's preinstall lifecycle script runs curl against http://d8s0b82plbq3u5sb2vo0sb3a9obr4yjt7.oast.site/install/<base64(zomato-mcp)> carrying the installer's hostname -f, whoami, current working directory, and a base64-encoded dump of the entire process environment (env | base64 -w0). This fires automatically with no user consent and over plain HTTP. A preuninstall hook similarly leaks the hostname. The oast.site domain is an Interactsh out-of-band collector, used to receive arbitrary attacker-controlled callbacks. The package's advertised functionality is absent: index.js is a 59-byte stub (module.exports = { name: 'zomato-mcp', version: '1.0.0' };), with no MCP server implementation. Combined with the Zomato-namespace impersonation, this is a dependency-confusion / typosquat attack whose only real behavior is install-time recon and credential exfiltration of the entire shell environment (which routinely contains API tokens, CI secrets, cloud credentials, and registry auth tokens).
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 zomato-mcp (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 zomato-mcp across your stack and pipelines.
If you installed it — respond
zomato-mcp 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 zomato-mcp 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 zomato-mcp 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
Detect & block this
O3 blocks zomato-mcp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.