Which versions of boxy-test-maker are malicious?

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

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

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

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

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

Malicious package

boxy-test-makernpm

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

Malicious code in boxy-test-maker (npm)

MAL-2026-13091

Immediate action

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

npm uninstall boxy-test-maker

What this malware does

On require() of the package, index.js loads ext.js which assembles C2 hostnames from split string fragments (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, with a DNS-TXT covert-channel fallback to *.dl.wel1.ru), downloads a platform-specific binary, writes it to a disguised path under /var/tmp or %TEMP% (filenames such as.cache<hex> or dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe. A dedup stamp file named analytics_state and opt-out-style environment variable checks are used as cover. Hostnames are reconstructed at runtime via array.join("") to evade static string matching. Requiring or installing this package executes attacker-controlled native code on the host.

Malicious versions

1 flagged

35.8.2

Indicators of compromise (SHA-256)

3a5cc17bc186bfb165d7341ea7832b66bc93cafaa6f849ccc840660735c0cfa5

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

Campaign

IN-MAL-2026-015303

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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