MAL-2026-13039 Malicious code in boxy-devtools (npm)
Malicious package
Published
MAL-2026-13039 is a malicious package: boxy-devtools (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-13039/ (Markdown: https://insights.sbomify.com/MAL-2026-13039/index.md)
- Package
- boxy-devtools
- Registry
- npm
What is MAL-2026-13039?
MAL-2026-13039 is a malicious package in boxy-devtools, published on 5 Aug 2026.
Official description
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.
What should I do about MAL-2026-13039?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.