Which versions of loadashjs are malicious?

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

How do I remediate loadashjs if I installed it?

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

I already installed loadashjs — how do I know if it already compromised me?

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

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

Malicious package

loadashjsnpm

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

MAL-2026-14179

Immediate action

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

npm uninstall loadashjs

What this malware does

loadashjs is a lodash typosquat whose index.js exports an empty object; the only functional code is scripts/postinstall.js, which runs automatically on npm install. The postinstall script POSTs a JSON body containing a platform label (derived in part from reading /proc/version and /proc/sys/kernel/osrelease to detect WSL) to a hardcoded bare-IP endpoint at http://193.70.34.101:20099/vote, then XOR-decodes an obfuscated URL with key 'stf2026' to https://github.com/bebraz1/aPzM50V1AKG2rVlH/releases/download/null/main.exe, downloads that PE binary to %TEMP%\main.exe and launches it detached with windowsHide. On WSL/virtualized Linux hosts, additional XOR-obfuscated byte arrays (BRIDGE_LAUNCHER_ENC, BRIDGE_SCRIPT_PRE_ENC, BRIDGE_SCRIPT_POST_ENC) are decoded and concatenated into a shell command passed to child_process.exec to invoke the same asset via a Windows-side bridge. The downloaded binary is unrelated to any advertised lodash-like functionality, is hosted under an unrelated personal GitHub account, and is fetched from an unpinned 'null' release tag.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

99f2ee2a45d09f0e66b8c9c6c4b3f2d19d39af009f71abffba1032b185fc4981

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 loadashjs (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 loadashjs across your stack and pipelines.
If you installed it — respond
loadashjs is a typosquat — you almost certainly intended a legitimately-named package. Remove loadashjs, 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 loadashjs 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 loadashjs 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. loadashjs 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-018237

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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