MAL-2026-14178 Malicious code in ladash-cli (npm)
Malicious package
Published
MAL-2026-14178 is a malicious package: ladash-cli (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-14178/ (Markdown: https://insights.sbomify.com/MAL-2026-14178/index.md)
- Package
- ladash-cli
- Registry
- npm
What is MAL-2026-14178?
MAL-2026-14178 is a malicious package in ladash-cli, published on 18 Aug 2026.
Official description
ladash-cli is a one-character typosquat of lodash-cli whose main entry exports an empty object; the only functional code is scripts/postinstall.js, which runs on npm install. The postinstall XOR-decodes (key 'stf2026') a hidden URL to https://github.com/bebraz1/qPzM50V1AKG0rVlH/releases/download/null/main.exe, downloads it to %TEMP%\main.exe, and spawns it detached with stdio ignored and windowsHide on win32 hosts, granting the publisher full-host code execution on the installer's machine. A WSL-detection branch inspects /proc/version and /proc/sys/kernel/osrelease for 'microsoft'/'WSL' and, when matched, decodes a PowerShell bridge command from further XOR-encoded byte arrays and exec()s it, delivering the same Windows executable to the underlying host from a Linux-WSL install. The postinstall also unconditionally POSTs a JSON platform label to http://193.70.34.101:20099/vote, using a bare IP assembled from a split string array over plain HTTP as an install beacon. The download URL, PowerShell command, and byte arrays are stored as XOR-encoded data with no hash or signature check, the release tag is 'null', and the GitHub account hosting the binary is unrelated to any lodash publisher.
What should I do about MAL-2026-14178?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.