Which versions of ladash-cli are malicious?

The following npm versions of ladash-cli are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ladash-cli if I installed it?

ladash-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed ladash-cli — how do I know if it already compromised me?

If ladash-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ladash-cli part of a known attack campaign?

Yes — ladash-cli is associated with the IN-MAL-2026-018236 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ladash-cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ladash-cli (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ladash-cli across your stack and pipelines.

Malicious package

ladash-clinpm

ladash-cli is a confirmed malicious npm package (MAL-2026-14178) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ladash-cli (npm)

MAL-2026-14178

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ladash-cli

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8d1b70674c7273e350d033cacec46a4981aebced798342e3b28da3dcd52a34bb

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ladash-cli (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ladash-cli across your stack and pipelines.
If you installed it — respond
ladash-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ladash-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ladash-cli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ladash-cli on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018236

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ladash-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database