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

express-devernpm

Advisory published Updated

express-dever is a confirmed malicious npm package (MAL-2026-13368) that executes malicious code on install (malicious versions 5.1.7, 5.1.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-dever (npm)

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

What this malware does

[email protected] registers postinstall: node index.js in package.json, and index.js is heavily obfuscated (obfuscator.io-style rotated string array with RC4/base64 decoders, hex-numeric constant folding, _0x variable naming, control-flow flattening). Decoded, the script requires axios/fs/path/child_process/os, constructs a dotted-quad host string at runtime via repeated .concat(x, '.') calls, performs axios.get(<url>), writes the response body to a file under process.cwd() with {flag:'w+'}, and spawns the written file via child_process with windowsHide:true. This is a download-and-execute dropper that fires automatically on npm install. Corroborating signals: package.json declares a self-referential floating dependency (express-dever: ^5.1.7), author and description fields are blank, and the README instructs readers to sandbox the file — consistent with a throwaway malicious upload rather than a legitimate library.

Malicious versions

2 flagged
5.1.75.1.8

Indicators of compromise (SHA-256)

e127c5f6a6747ae491acb2166ed55c1e6aba47aca1166ade97bf084b5dbbce31
f4bad4e01b45f62041b732eb4315d326e2411d5fc09889818568459ae4ec77c7

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for express-dever (2 malicious versions).

  2. If you installed it — respond

    Remove express-dever from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

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

Campaign

IN-MAL-2026-015879IN-MAL-2026-015857

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks express-dever-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

express-dever (npm) malicious package — MAL-2026-13368 | O3 Security