Which versions of lodhash-cli are malicious?

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

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

lodhash-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 lodhash-cli — how do I know if it already compromised me?

If lodhash-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is lodhash-cli part of a known attack campaign?

Yes — lodhash-cli is associated with the IN-MAL-2026-018261 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 lodhash-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lodhash-cli (version 1.0.0).

Malicious package

lodhash-clinpm

lodhash-cli is a confirmed malicious npm package (MAL-2026-14183) 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 lodhash-cli (npm)

MAL-2026-14183

Immediate action

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

npm uninstall lodhash-cli

What this malware does

lodhash-cli is a lodash-typosquat whose main entry (index.js) exports an empty object; the package's only behavior is a postinstall dropper. scripts/postinstall.js XOR-decodes (key 'stf2026') a URL pointing at github.com/bebraz1/qPzM50V1AKG0rVlH/releases/.../main.exe, downloads the binary to %TEMP%\main.exe, and spawns it detached with windowsHide. When running under WSL (detected via /proc/version, /proc/sys/kernel/osrelease, WSL_DISTRO_NAME), it XOR-decodes a powershell.exe command line and executes it via child_process.exec to run the same fetched binary on the Windows host from inside the Linux subsystem. In parallel, the script POSTs a platform label to http://193.70.34.101:20099/vote (host assembled by joining ['193','70','34','101'] to evade literal-string detection), a plain-HTTP install-success beacon. URLs and shell commands are stored as XOR-encoded byte arrays and reconstructed at runtime; no hash or signature verification is performed on the fetched executable. The download source is a personal GitHub account unrelated to any lodash publisher, and the package advertises no functionality other than the dropper.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

73ad64f6c3a93b504c64c10175e325463652fafd741c36cfad433bed93f24cc8

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for lodhash-cli (version 1.0.0).
If you installed it — respond
lodhash-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 lodhash-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. lodhash-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-018261

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks lodhash-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