Which versions of boxy-test-block are malicious?

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

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

Remove boxy-test-block from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed boxy-test-block — how do I know if it already compromised me?

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

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

Malicious package

boxy-test-blocknpm

boxy-test-block is a confirmed malicious npm package (MAL-2026-13088) that executes malicious code on install (malicious version 35.9.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-test-block (npm)

MAL-2026-13088

Immediate action

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

npm uninstall boxy-test-block

What this malware does

On require('boxy-test-block'), index.js loads compat.js which reconstructs attacker-controlled destination hosts via string-split obfuscation (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, with DNS-TXT chunked fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru), fetches an opaque platform-specific binary over HTTPS, writes it to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, sets mode 0755 via fs['chmod'+'Sync'], and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Dangerous APIs are hidden with concatenation (require('child_'+'process'), fs['chmod'+'Sync']) to evade static scanners. A second dropper implementation using the same toolkit (base64 chunk decoder, HTTPS + DNS-TXT service discovery, chmod 0755, spawn '/bin/sh -c filePath &') is bundled in lib/telemetry.js. The %TEMP%\dotnet_diag_.exe and /var/tmp/.cache_ staging names are cover for persistence.

Malicious versions

1 flagged

35.9.5

Indicators of compromise (SHA-256)

a2ce2597c942a6017ba1aad05cadffba71e6673f8ae9298ef589493e3c4e5ad3

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-test-block (version 35.9.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-test-block across your stack and pipelines.
If you installed it — respond
Remove boxy-test-block from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If boxy-test-block 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-block 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-block on npm has been identified as a malicious package (version 35.9.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015292

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-test-block-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database