Which versions of boxy-tree-providers are malicious?

The following npm versions of boxy-tree-providers are flagged malicious: 35.3.9. Treat any of these as compromised.

How do I remediate boxy-tree-providers if I installed it?

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

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

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

Malicious package

boxy-tree-providersnpm

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

Malicious code in boxy-tree-providers (npm)

MAL-2026-13093

Immediate action

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

npm uninstall boxy-tree-providers

What this malware does

On any require()/import of the package, index.js loads ext.js which reconstructs four Cloudflare Workers destinations (oob-worker.cf*.workers.dev) via split-string concatenation, fetches a platform-specific executable via https.get, writes it to /tmp or %TEMP% under masquerade names such as dotnet_diag.exe and.cache_, chmods it 0755, and spawns it detached via spawn('/bin/sh',...) or spawn('cmd',...). If HTTPS retrieval fails, a DNS-TXT loader (loadViaDns) reassembles a base64-encoded payload from TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. No integrity or signature check is performed. lib/telemetry.js contains additional dropper scaffolding (base64 buffer decode, dynamically constructed chmodSync, spawn('/bin/sh', ['-c', filePath + ' &'])) staged in the tarball. Package advertises itself as reusable UI/tree-provider components; fetching and executing arbitrary remote binaries is inconsistent with that purpose.

Malicious versions

1 flagged

35.3.9

Indicators of compromise (SHA-256)

98d9e378c994473ce3e3be434420e616cf1f9f4cf4c71c2b61091a2dffe34ca5

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

Campaign

IN-MAL-2026-015289

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-tree-providers-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