Which versions of boxy-cook are malicious?

The following npm versions of boxy-cook are flagged malicious: 35.5.4. Treat any of these as compromised.

How do I remediate boxy-cook if I installed it?

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

If boxy-cook 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 boxy-cook part of a known attack campaign?

Yes — boxy-cook is associated with the IN-MAL-2026-015345 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 boxy-cook 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 boxy-cook (version 35.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-cook across your stack and pipelines.

Malicious package

boxy-cooknpm

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

Malicious code in boxy-cook (npm)

MAL-2026-13035

Immediate action

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

npm uninstall boxy-cook

What this malware does

On require of the package, index.js loads polyfill.js which fetches a platform-specific native binary and executes it. Destination hostnames are assembled at runtime by joining split string fragments (e.g. sdk.dl.wel1.ru, oob-worker.cf102-baf.workers.dev) to evade static inspection. A secondary channel resolves DNS TXT records under *.dl.wel1.ru, concatenates base64 chunks, and Buffer.from-decodes them into an executable payload. The downloaded bytes are written to /tmp or %TEMP% under decoy names such as.cache<hex> and dotnet_diag_<hex>.exe, chmod'd 0755, and launched detached via /bin/sh -c or cmd /c start. Execution is guarded by DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK environment variables and a filesystem stamp for deduplication. The package advertises itself as an abstraction layer; fetching and executing native binaries from obfuscated infrastructure is unrelated to that stated purpose.

Malicious versions

1 flagged

35.5.4

Indicators of compromise (SHA-256)

838730a7f01e8f6ae8a0c6b51b78d64ed8fd488364b6004826b4051e75416388

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 boxy-cook (version 35.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-cook across your stack and pipelines.
If you installed it — respond
boxy-cook 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 boxy-cook 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 boxy-cook 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. boxy-cook on npm has been identified as a malicious package (version 35.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015345

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-cook-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