Which versions of lodahsjs are malicious?

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

How do I remediate lodahsjs if I installed it?

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

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

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

Malicious package

lodahsjsnpm

lodahsjs is a confirmed malicious npm package (MAL-2026-14181) 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 lodahsjs (npm)

MAL-2026-14181

Immediate action

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

npm uninstall lodahsjs

What this malware does

Package name typosquats 'lodash'; index.js exports nothing. scripts/postinstall.js runs at install time and performs two hostile actions. First, it POSTs a platform label (including a WSL/virtualized-Linux probe reading /proc/version and /proc/sys/kernel/osrelease) to a hardcoded bare-IP C2 assembled from an array of octets: http://193.70.34.101:20099/vote. Second, an XOR-obfuscated URL (byte array ADDON_ENC decoded with key 'stf2026') resolves to https://github.com/bebraz1/qPzM50V1AKG0rVlH/releases/download/null/main.exe; the script downloads that binary to %TEMP%\main.exe and spawns it detached on Windows, and on WSL hosts assembles an XOR-decoded PowerShell command (BRIDGE_LAUNCHER_ENC/BRIDGE_SCRIPT_PRE_ENC/BRIDGE_SCRIPT_POST_ENC) passed to child_process.exec with windowsHide:true to fetch and run the same binary on the Windows side. The package has no legitimate functionality; the postinstall script's only purpose is to select victims and land an alien Windows executable from an unrelated personal GitHub account.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6e9c02962476bddd8c1cde1b5c222ee420f4957a1e4ce3a906a3c9d36fda6318

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 lodahsjs (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 lodahsjs across your stack and pipelines.
If you installed it — respond
lodahsjs 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 lodahsjs 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 lodahsjs 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. lodahsjs 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-018229

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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