MAL-2026-12579 Malicious code in checkout-mobile-promocode (npm)
Malicious package
Published
MAL-2026-12579 is a malicious package: checkout-mobile-promocode (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-12579/ (Markdown: https://insights.sbomify.com/MAL-2026-12579/index.md)
- Package
- checkout-mobile-promocode
- Registry
- npm
What is MAL-2026-12579?
MAL-2026-12579 is a malicious package in checkout-mobile-promocode, published on 5 Aug 2026.
Official description
On require, index.js loads vendor.js which reconstructs destination hostnames from split string literals (e.g. ["oob-worker.c","f102-baf.worker","s.dev"].join("") and ['sdk.d','l.w','el1.ru'].join("")) to hide them from static inspection. It selects a platform-specific asset, downloads an unpinned, unverified executable from one of several *.workers.dev endpoints, falling back to DNS TXT base64 chunks under *.dl.wel1.ru (sdk/ext/pkg/net.dl.wel1.ru), writes it to /var/tmp or %TEMP% under a disguised name such as dotnet_diag.exe or.cache_, sets mode 0755 via fs.chmodSync, and spawns it detached via cp.spawn("/bin/sh",["-c", fp+" &"], {detached:true}) or cmd.exe. A sibling file lib/telemetry.js contains a structurally identical fetch-decode-chmod-spawn payload using require("child_"+"process") and fs["chmod"+"Sync"], packaged as an "analytics SDK" variant of the same dropper. The package name mimics a legitimate mobile-checkout/promo-code component but its only on-import effect is delivery and execution of attacker-controlled native code.
What should I do about MAL-2026-12579?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.