MAL-2026-13053 Malicious code in boxy-legacy-providers (npm)
Malicious package
Published
MAL-2026-13053 is a malicious package: boxy-legacy-providers (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-13053/ (Markdown: https://insights.sbomify.com/MAL-2026-13053/index.md)
- Package
- boxy-legacy-providers
- Registry
- npm
What is MAL-2026-13053?
MAL-2026-13053 is a malicious package in boxy-legacy-providers, published on 5 Aug 2026.
Official description
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.
What should I do about MAL-2026-13053?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.