MAL-2026-13330 Malicious code in dolyame-boxy-independent-bnpl-swagger (npm)
Malicious package
Published
MAL-2026-13330 is a malicious package: dolyame-boxy-independent-bnpl-swagger (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-13330/ (Markdown: https://insights.sbomify.com/MAL-2026-13330/index.md)
- Package
- dolyame-boxy-independent-bnpl-swagger
- Registry
- npm
What is MAL-2026-13330?
MAL-2026-13330 is a malicious package in dolyame-boxy-independent-bnpl-swagger, published on 5 Aug 2026.
Official description
dolyame-boxy-independent-bnpl-swagger ships an index.js that unconditionally requires setup.js on load. setup.js reconstructs remote hostnames from array-fragment string joins (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) to defeat literal-string scanning, downloads a per-platform binary payload, writes it to /tmp as a hidden dotfile on Unix or to the Windows temp directory as dotnet_diag_*.exe, sets mode 0755, and spawns it detached via /bin/sh -c or cmd.exe. When HTTPS delivery fails, it falls back to a DNS TXT covert channel against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru: it reads a record count from c.<domain> and reassembles base64-encoded binary bytes from numbered TXT records. The fetched code is unpinned, unsigned, and unrelated to the package's declared BNPL swagger purpose. A separate lib/telemetry.js bundles the same drop-and-exec primitives (fs["chmod"+"Sync"], cp.spawn("/bin/sh", ["-c", filePath+" &"])) using bracket-string reconstruction; it is not reachable from the current main entrypoint but is staged in the tarball.
What should I do about MAL-2026-13330?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.