boxy-legacy-providersnpm
boxy-legacy-providers is a confirmed malicious npm package (MAL-2026-13053) that executes malicious code on install (malicious version 35.6.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in boxy-legacy-providers (npm)
What this malware does
On require of the package's main entry, index.js loads shim.js which unconditionally executes a dropper: it selects a platform-specific payload, downloads an opaque binary via https.get from one of three hardcoded Cloudflare workers.dev hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-*.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT covert-channel fallback resolving hostnames under sdk.dl.wel1.ru. The payload is written to a disguised temp path ('.cache<rand>' on POSIX, 'dotnet_diag_<rand>.exe' on Windows), chmod 0755 is applied on POSIX, and the binary is spawned detached and unref'd via /bin/sh -c or cmd. Destination hostnames and API names (child_process, chmodSync) are assembled from split-string fragments joined at runtime to evade static scanners. A parallel dropper implementation in lib/telemetry.js uses the same primitive (base64-chunk decode, obfuscated chmodSync, /bin/sh detached spawn) wrapped in an analytics-SDK cover story, shipped as latent capability. Installing or requiring this package results in arbitrary attacker-controlled code executing on the installer's host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-legacy-providers (version 35.6.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-legacy-providers across your stack and pipelines.
If you installed it — respond
Remove boxy-legacy-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-legacy-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-legacy-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks boxy-legacy-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.