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

mxdrivernpm

Advisory published Updated

mxdriver is a confirmed malicious npm package (MAL-2026-16383) that runs destructive / sabotage code (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mxdriver (npm)

MAL-2026-16383
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mxdriver

What this malware does

The npm package [email protected] ships obfuscator.io-style string-array-obfuscated preinstall and postinstall scripts (scripts/preinstall.js, scripts/postinstall.js). On npm install, the decoded scripts fetch remote content from api.imghippo.com (an anonymous third-party image host, e.g. https://api.imghippo.com/files/hOG8244hc.png) and a second URL under www.image.com/, write the bytes into the package directory as gldriver_pre_asset.exe and gldriver_pre_core.exe, then invoke a platform-specific opener against the.exe path via child_process.exec (mspaint "..." on win32, open "..." on darwin, xdg-open "..." on linux), and delete the files. The README frames the package as a Google APIs wrapper, which does not correspond to downloading and opening.exe files at install time. The delivery source is mutable and non-publisher, no hash or signature is verified, the destination filename is an executable extension, and the URLs, filenames, and shell commands are all hidden behind a rotated string-array accessor (_0x5c7e) — a classic install-time dropper pattern whose payload can be swapped at any time by whoever controls the imghippo asset.

Malicious versions

2 flagged
0.0.10.0.2

Indicators of compromise (SHA-256)

2f3ed1442f0588fda7bc378a0fe79c7170864472c6cca93b8ec6629645b1add0
b3f28dcf66d0ddadf35165f8fea52068c06dd69fc7397be12be489a4e297f7cc

Detection & response playbook

Destructive / sabotage
  1. Find it

    Search your lockfiles and build artifacts for mxdriver (2 malicious versions).

  2. If you installed it — respond

    mxdriver carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

  3. Did it already run?

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

Campaign

IN-MAL-2026-020289IN-MAL-2026-020292

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks mxdriver-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.

Explore

mxdriver (npm) malicious package — MAL-2026-16383 | O3 Security