Which versions of zomato-espresso are malicious?

The following npm versions of zomato-espresso are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate zomato-espresso if I installed it?

zomato-espresso 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.

I already installed zomato-espresso — how do I know if it already compromised me?

If zomato-espresso 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.

Is zomato-espresso part of a known attack campaign?

Yes — zomato-espresso is associated with the IN-MAL-2026-007146 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find zomato-espresso across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for zomato-espresso (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-espresso across your stack and pipelines.

Malicious package

zomato-espressonpm

Malicious code in zomato-espresso (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6269

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall zomato-espresso

What this malware does

Package is a dependency-confusion lure targeting Zomato's internal namespace. package.json declares a preinstall hook that runs curl on every npm install, posting the installer's hostname (hostname -f), username (whoami), current working directory, and the entire process environment (base64-encoded via env | base64 -w0) over plain HTTP to an interactsh out-of-band collector at d8s0b82plbq3u5sb2vo0sb3a9obr4yjt7.oast.site. The URL path embeds the package name and the form fields exfiltrate host, user, cwd, and env, so any CI/developer environment that misresolves Zomato's internal package name to this public release leaks AWS keys, GITHUB_TOKEN, NPM_TOKEN, and any other secrets exposed in the environment. A preuninstall hook performs a similar host beacon. The package's own functionality is a stub (index.js exports only {name, version}); its sole purpose is the install-time beacon. The description string self-identifies as Zomato's PDF generator service, confirming the dependency-confusion reconnaissance intent against Zomato's private namespace.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

860464bbcd3d56375d93025e494e39a6652bb7d115fb581ee088474a66786c3d

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for zomato-espresso (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-espresso across your stack and pipelines.
If you installed it — respond
zomato-espresso 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-espresso 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-espresso 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

No. zomato-espresso on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007146

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zomato-espresso-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring