MAL-2026-14173 Malicious code in commandor-core (npm)
Malicious package
Published
MAL-2026-14173 is a malicious package: commandor-core (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-14173/ (Markdown: https://insights.sbomify.com/MAL-2026-14173/index.md)
- Package
- commandor-core
- Registry
- npm
What is MAL-2026-14173?
MAL-2026-14173 is a malicious package in commandor-core, published on 18 Aug 2026.
Official description
The postinstall script in [email protected] (scripts/postinstall.js) contains XOR-obfuscated byte arrays that decode at runtime (unpackSegment with key 'stf2026') to a download URL at giphub.com — a typosquat of github.com — pointing at https://giphub.com/bebraz1/PzM50V1AKG0rVlH/releases/download/null/main.exe. On Windows the script fetches main.exe into %TEMP% and spawns it detached; on WSL it decodes and invokes a PowerShell bridge command to execute the fetched binary on the Windows host. The same postinstall unconditionally POSTs a JSON body describing the host platform to a hardcoded bare-IP endpoint at http://193.70.34.101:20099/vote (assembled from a four-element array to defeat literal-IP scans) over plain HTTP. The main entry index.js is empty; the package provides no library functionality, and the sole effect of
npm install commandor-core is beaconing the host and dropping and executing an attacker-controlled Windows executable.What should I do about MAL-2026-14173?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.