express-devernpm
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for express-dever (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-dever across your stack and pipelines.
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.
Did it already run?
If express-dever 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 express-dever 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
Campaign
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.