MAL-2026-12574 Malicious code in checkout-mobile-dolyame (npm)
Malicious package
Published
MAL-2026-12574 is a malicious package: checkout-mobile-dolyame (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-12574/ (Markdown: https://insights.sbomify.com/MAL-2026-12574/index.md)
- Package
- checkout-mobile-dolyame
- Registry
- npm
What is MAL-2026-12574?
MAL-2026-12574 is a malicious package in checkout-mobile-dolyame, published on 5 Aug 2026.
Official description
Requiring checkout-mobile-dolyame loads loader.js via index.js, which selects an OS/arch-specific binary and downloads it over HTTPS from obfuscated Cloudflare workers.dev mirrors (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) whose hostnames are reconstructed at runtime from split-string fragments joined with.join(''). A fallback delivery channel resolves DNS TXT records under c.<domain> and N.<domain> (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) to reassemble a base64-encoded payload, evading URL/domain filtering. The downloaded bytes are written to /var/tmp or %TEMP% under masqueraded names (.cache<hex> or dotnet_diag_<hex>.exe), chmod 0755, then spawned detached via /bin/sh -c '<file> &' or cmd.exe /c start /b with stdio ignored. No hash or signature verification is performed. The name resembles legitimate Dolyame checkout tooling, but the package's only observable behavior on import is downloading and running arbitrary attacker-supplied code.
What should I do about MAL-2026-12574?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.