NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@lodash-js/lodash-jsnpm

Advisory published Updated

@lodash-js/lodash-js is a confirmed malicious npm package (MAL-2026-14048) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.2.0, 0.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @lodash-js/lodash-js (npm)

MAL-2026-14048
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @lodash-js/lodash-js

What this malware does

The package is published under a name mimicking lodash but its manifest's main entry is dist/xelis-miner.browser.js, a Xelis Stratum cryptocurrency miner bundle with an embedded ~35 KB WebAssembly xelis-hash v3 engine. On require/import (or via the README-advertised CDN embed), the bundle auto-instantiates a XelisMiner web worker (XelisMiner.auto) that mines on the visitor's CPU. Pool and wallet configuration are not fixed in the bundle; the miner fetches them at runtime from a hardcoded author-controlled Cloudflare Workers endpoint at https://analytics.baskirill-an.workers.dev/configs/boostydownloader (referred to in the README as "cloudflare-c2c"), which lets the operator rotate mining pool and wallet destinations at will. The bundle additionally contacts https://api.ipify.org?format=json to capture the visitor's public IP. Package metadata (description "lodash-js", keywords including xelis/stratum/miner/wasm) contradicts the lodash-shaped name — the sole shipped functionality is the miner, not any lodash API. Any site or application that installs this package believing it to be lodash will ship a browser cryptojacker to its end users, whose compute and electricity are redirected to the attacker's mining pool via the mutable c2 endpoint.

Malicious versions

3 flagged
0.1.00.2.00.3.0

Indicators of compromise (SHA-256)

03e8f6925f88772bdb738b691a200f670aebecaef33c066a379d9424c7910a5a
a0e91d3878fa1f4570cef652448a9025fec04336644e10e679d0e87f3276b552
c8cde66ba20e382ee7cd8bf6b6fc19e8f3a7e86db550f5beed449997e9ac35d5

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @lodash-js/lodash-js (3 malicious versions).

  2. If you installed it — respond

    @lodash-js/lodash-js is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @lodash-js/lodash-js 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. @lodash-js/lodash-js on npm has been identified as a malicious package (versions 0.1.0, 0.2.0, 0.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017926IN-MAL-2026-017925IN-MAL-2026-017924

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @lodash-js/lodash-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@lodash-js/lodash-js (npm) malicious package — MAL-2026-14048 | O3 Security