Which versions of boxy-sitree are malicious?

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

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

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

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

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

Malicious package

boxy-sitreenpm

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

Malicious code in boxy-sitree (npm)

MAL-2026-13083

Immediate action

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

npm uninstall boxy-sitree

What this malware does

Requiring boxy-sitree triggers _shim.js, which selects a platform-specific binary path, fetches an executable from Cloudflare Workers hosts assembled by joining string fragments (oob-worker.cf*-*.workers.dev) with a DNS-TXT covert channel fallback that reassembles base64 chunks from numbered subdomains of *.dl.wel1.ru, writes the bytes to a temp file, chmods 0755, and spawns the binary detached via /bin/sh -c '<file> &' on Unix or cmd.exe start /b on Windows. Host and domain strings are split to defeat static matching, and the dropper is wrapped in analytics/diagnostics cover-story naming with opt-out environment variables. A second, unreferenced module lib/telemetry.js contains the same shell-spawn + chmod 0755 + base64 payload staging pattern under an 'Analytics SDK' framing, indicating a staged/parallel payload from the same actor. Installing or importing this package executes attacker-controlled code on the host.

Malicious versions

1 flagged

35.8.7

Indicators of compromise (SHA-256)

2be12f6af3487a38f7fa17ee8a4fd8a910f9dccffa351a8e19545781b2dfd3bc

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

Campaign

IN-MAL-2026-015297

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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