MAL-2026-13065 Malicious code in boxy-maker-sticky (npm)
Malicious package
Published
MAL-2026-13065 is a malicious package: boxy-maker-sticky (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-13065/ (Markdown: https://insights.sbomify.com/MAL-2026-13065/index.md)
- Package
- boxy-maker-sticky
- Registry
- npm
What is MAL-2026-13065?
MAL-2026-13065 is a malicious package in boxy-maker-sticky, published on 5 Aug 2026.
Official description
On require() of boxy-maker-sticky, index.js loads runtime.js which reconstructs C2 hostnames from split string fragments ("oob-worker.cf103-0"+"70.worke"+"rs.dev" and "sdk.dl.we"+"l1.ru"), performs an https.get against those hosts to download a platform-specific binary, writes it to a temp directory under a disguised filename (dotnet_diag<rand>.exe on Windows,.cache_<rand> on POSIX), chmods it 0755, and spawns it detached via cmd.exe or /bin/sh -c with.unref(). A DNS-TXT chunked fallback path resolves further payload data through *.dl.wel1.ru. A.analytics_state file is written as a persistence/timestamp marker. The fetched content is unpinned, unverified, and unrelated to any stated package purpose; hostname obfuscation via runtime string joining is deliberate evasion. The behavior fires automatically on module load, giving whoever controls the origin hosts arbitrary code execution on the installer's machine.
What should I do about MAL-2026-13065?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.