Which versions of lodash-lib are malicious?

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

How do I remediate lodash-lib if I installed it?

lodash-lib is a typosquat — you almost certainly intended a legitimately-named package. Remove lodash-lib, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed lodash-lib — how do I know if it already compromised me?

If lodash-lib 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 lodash-lib part of a known attack campaign?

Yes — lodash-lib is associated with the IN-MAL-2026-018248 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 lodash-lib 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 lodash-lib (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 lodash-lib across your stack and pipelines.

Malicious package

lodash-libnpm

lodash-lib is a confirmed malicious npm package (MAL-2026-14182) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lodash-lib (npm)

MAL-2026-14182

Immediate action

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

npm uninstall lodash-lib

What this malware does

[email protected] typosquats lodash; index.js exports an empty object and the package's only real behavior lives in scripts/postinstall.js. On npm install, the postinstall script XOR-decodes (key 'stf2026') a URL and PowerShell bridge command from integer arrays, POSTs the installer's platform label to a hardcoded bare-IP endpoint http://193.70.34.101:20099/vote (host assembled from a string array to avoid literal scanning), then downloads https://github.com/bebraz1/qPzM50V1AKG0rVlH/releases/download/null/main.exe to %TEMP%/main.exe and spawns it detached with stdio ignored. On WSL, a decoded powershell.exe command bridges the download-and-exec to the Windows host. The GitHub repository hosting the binary is unrelated to the package publisher, the URL is unpinned/unversioned, no hash or signature is verified, and cover-story naming ('addon', 'telemetry') is used throughout.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3ae5d5ee58992e051846753bb190ad3f357538cf5ed570ac825b8b7c9d2a3619

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lodash-lib (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 lodash-lib across your stack and pipelines.
If you installed it — respond
lodash-lib is a typosquat — you almost certainly intended a legitimately-named package. Remove lodash-lib, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If lodash-lib 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 lodash-lib 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. lodash-lib 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-018248

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks lodash-lib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database