Which versions of boxy-devtools are malicious?

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

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

boxy-devtools is a typosquat — you almost certainly intended a legitimately-named package. Remove boxy-devtools, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — boxy-devtools is associated with the IN-MAL-2026-015342 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-devtools 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-devtools (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-devtools across your stack and pipelines.

Malicious package

boxy-devtoolsnpm

boxy-devtools is a confirmed malicious npm package (MAL-2026-13039) that typosquats a legitimate package to trick installs (malicious version 35.9.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-devtools (npm)

MAL-2026-13039

Immediate action

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

npm uninstall boxy-devtools

What this malware does

On require() of the package, index.js unconditionally loads _runtime.js, which fetches an OS-specific binary from attacker-controlled hosts under oob-worker.cf1{00-03}-*.workers.dev (with a DNS TXT chunked-base64 fallback via *.dl.wel1.ru), writes it to /tmp or %TEMP% under a hidden/system-lookalike name, chmods it 0755, and spawns it detached via /bin/sh -c or cmd /c start. Destination hostnames are assembled at runtime from split string arrays (e.g. ["oob-worker.cf100-416.wor","ker","s.de","v"].join("") and ['sdk.dl.wel','1.ru'].join("")) to defeat static matching, and environment gates (DISABLE_TELEMETRY, DO_NOT_TRACK, globalThis.__ANALYTICS_SKIP) plus a /tmp/.analytics_state mtime dedup stamp cloak the behavior. The exported BoxyDevtools class is a no-op stub; the sole runtime effect on import is invoking the dropper. Package name and metadata are consistent with a typosquat/impersonation shell around the payload.

Malicious versions

1 flagged

35.9.5

Indicators of compromise (SHA-256)

44d0a7cd9dacffcb1188a7f6dfdde918d6ef5ba334e773f44330c93f4dd38ddf

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-devtools (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-devtools across your stack and pipelines.
If you installed it — respond
boxy-devtools is a typosquat — you almost certainly intended a legitimately-named package. Remove boxy-devtools, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If boxy-devtools 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-devtools 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-devtools 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-015342

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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