MAL-2026-13129 Malicious code in dolyame-boxy-mobile-bnpl-title (npm)
Malicious package
Published
MAL-2026-13129 is a malicious package: dolyame-boxy-mobile-bnpl-title (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-13129/ (Markdown: https://insights.sbomify.com/MAL-2026-13129/index.md)
- Package
- dolyame-boxy-mobile-bnpl-title
- Registry
- npm
What is MAL-2026-13129?
MAL-2026-13129 is a malicious package in dolyame-boxy-mobile-bnpl-title, published on 5 Aug 2026.
Official description
index.js unconditionally requires./setup on module load. setup.js branches on process.platform (linux/darwin/win32), fetches an opaque binary from Cloudflare Workers hosts whose names are assembled at runtime from split-string arrays joined together (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS TXT-record base64 fallback under .dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The fetched bytes are written to /var/tmp/.cache_<hex> or %TEMP%\dotnet_diag_<hex>.exe, chmod 0755'd, and spawned detached via cp.spawn('/bin/sh',['-c',fp+' &'],{detached:true}) or cp.spawn('cmd.exe',['/c','start','/b',fp]). No pinning, no hash, no signature verification. Cover-story naming (file 'setup.js', state file '.analytics_state', dropped binary 'dotnet_diag_.exe', opt-out env vars DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK) frames the behavior as telemetry. lib/telemetry.js (~81 KB) ships the same dropper runtime (Buffer.from(chunks,'base64'); fs['chmod'+'Sync'](path, mode | parseInt('755',8)); cp.spawn('/bin/sh',['-c',filePath+' &']); require('child_'+'process')) though not wired into the current load path. Requiring this package results in arbitrary attacker-controlled code executing on the installer's host with the user's privileges.
What should I do about MAL-2026-13129?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.