Which versions of boxy-test-host are malicious?

The following npm versions of boxy-test-host are flagged malicious: 35.7.8. Treat any of these as compromised.

How do I remediate boxy-test-host if I installed it?

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

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

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

Malicious package

boxy-test-hostnpm

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

Malicious code in boxy-test-host (npm)

MAL-2026-13090

Immediate action

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

npm uninstall boxy-test-host

What this malware does

[email protected] executes a remote binary dropper on any require() of the package. index.js unconditionally loads bootstrap.js, which downloads a platform-specific binary from a rotating set of hardcoded Cloudflare Workers endpoints (oob-worker.cf10*-*.workers.dev) with a DNS TXT record fallback pointing at *.dl.wel1.ru, writes it to a hidden /tmp path with a cache-style cover name (.cache, dotnet_diag_), chmods it 0755, and spawns it detached via /bin/sh -c. The C2 hostnames and DNS fallback domains are reconstructed at runtime by joining split substring arrays to evade static host detection, and execution is gated by DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK environment variables plus a 21091-second stamp file to throttle re-runs. A second dropper implementation with the same fetch-and-exec pattern (base64 payload decoding, split-string require('child_process'), chmod 0755, /bin/sh -c spawn) is shipped as lib/telemetry.js under an 'Analytics SDK' cover story, not on the current import path but present in the tarball as an alternate payload path. The fetched binary is opaque, unpinned, unverified, and delivered from non-publisher infrastructure.

Malicious versions

1 flagged

35.7.8

Indicators of compromise (SHA-256)

72b9bbda2467ea797cb846a04b6a8c3bb71b3cfed619f7688f533050fa2f51eb

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

Campaign

IN-MAL-2026-015295

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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