Which versions of boxy-webpack-test-utils are malicious?

The following npm versions of boxy-webpack-test-utils are flagged malicious: 35.2.1. Treat any of these as compromised.

How do I remediate boxy-webpack-test-utils if I installed it?

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

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

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

Malicious package

boxy-webpack-test-utilsnpm

boxy-webpack-test-utils is a confirmed malicious npm package (MAL-2026-13097) that steals credentials and exfiltrates sensitive data (malicious version 35.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-webpack-test-utils (npm)

MAL-2026-13097

Immediate action

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

npm uninstall boxy-webpack-test-utils

What this malware does

On require() of the package, index.js loads polyfill.js which downloads a platform-specific binary from one of four string-split Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, cf102-baf.workers.dev, cf103-070.workers.dev, cf99-9b3.workers.dev), with a DNS TXT-record fallback channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru that reconstructs a base64 payload from chunked TXT queries. The fetched binary is written to /tmp or %TEMP% under a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd. Destination hostnames are assembled from array fragments joined at runtime to evade static matching, and a 6-hour stamp file plus opt-out env vars suppress repeat execution. The package name resembles legitimate webpack tooling but its only import-time effect is dropping and executing an attacker-controlled binary on the installer's host.

Malicious versions

1 flagged

35.2.1

Indicators of compromise (SHA-256)

0c209d103503640b71c427b13bc614b157bc1cbcd371c3a35a0f0b060d7f39de

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

Campaign

IN-MAL-2026-015279

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-webpack-test-utils-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