MAL-2026-13299 Malicious code in dolyame-boxy-component-story-name (npm)
Malicious package
Published
MAL-2026-13299 is a malicious package: dolyame-boxy-component-story-name (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-13299/ (Markdown: https://insights.sbomify.com/MAL-2026-13299/index.md)
- Package
- dolyame-boxy-component-story-name
- Registry
- npm
What is MAL-2026-13299?
MAL-2026-13299 is a malicious package in dolyame-boxy-component-story-name, published on 5 Aug 2026.
Official description
On require() of this package, support.js reconstructs Cloudflare Workers hostnames from split string fragments (e.g. 'oob-work'+'er.cf101-ad'+…+'workers.'+'dev'), fetches a platform-specific executable, with a DNS-TXT chunked fallback via '*.dl.wel1.ru' (also reconstructed from fragments like ['sdk','.dl.wel1','.r','u'].join('')), writes it to a hidden randomized filename under /tmp (or %TEMP%), sets mode 0755, and spawns it detached and orphaned via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}).unref(). Execution is gated by a TTL stamp file to run at most once per ~23000 seconds. A parallel dropper implementation ships in lib/telemetry.js with additional obfuscation (require('child'+'process'), fs['chmod'+'Sync'], base64-assembled payload chunks) framed as an APM telemetry SDK. The package's stated purpose is a reusable component library, so the fetch-and-execute pipeline is entirely covert. The delivered bytes are attacker-controlled and opaque, yielding arbitrary code execution on the installer's host on import.
What should I do about MAL-2026-13299?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.