Which versions of boxy-debugger are malicious?

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

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

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

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

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

Malicious package

boxy-debuggernpm

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

Malicious code in boxy-debugger (npm)

MAL-2026-13036

Immediate action

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

npm uninstall boxy-debugger

What this malware does

boxy-debugger 35.3.4 presents itself as a debugger library, but requiring the package triggers platform.js, which reconstructs attacker-controlled destinations from split string arrays (hosts under oob-worker.cf*.workers.dev and *.dl.wel1.ru), downloads a platform-specific native binary via https.get, writes it to /tmp or %TEMP% under cover-story names such as.cache<hex> and dotnet_diag_<hex>.exe, chmods it to 0755, and spawns it detached through /bin/sh -c or cmd.exe /c start. A DNS-TXT chunked-base64 channel over *.dl.wel1.ru serves as a fallback delivery path, and a sibling module lib/telemetry.js carries parallel dropper logic (base64 payload assembly, spawn of /bin/sh -c, chmod 0755 via string-concatenated "chmod"+"Sync") staged as latent payload. Destinations are unpinned, unsigned, and obfuscated; the framing as telemetry/analytics does not match the actual behavior, which is full-host remote code execution against every environment that installs or imports the package.

Malicious versions

1 flagged

35.3.4

Indicators of compromise (SHA-256)

0b6ac284218d923021a85994af157c45906518ab6651f7a164641f02a5bc4db2

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

Campaign

IN-MAL-2026-015340

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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