Malicious Code Execution Vulnerability in xeprews Package

xeprews Updated 29 Sep 2026

Summary

29/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17248: Malicious code in xeprews (npm). Affects xeprews versions 5.2.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The xeprews package is a typosquatted version of the popular Express framework, designed to mimic its functionality and attributes. It is intended for use in Node.js applications, providing web server capabilities similar to Express. However, due to its malicious nature, it poses significant security risks to users who mistakenly install it, believing it to be the legitimate Express package.

Vulnerability Detail

The xeprews package contains a preinstall lifecycle hook that executes a command to fetch and run a JavaScript file from a third-party source during installation. This behavior allows an attacker to execute arbitrary code on the installer's machine without their consent. The vulnerability originates from the package's impersonation of the legitimate Express framework, which can mislead users into installing it. The lack of integrity checks and the mutable nature of the source code further exacerbate the risk, allowing the attacker to modify the code at any time.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall xeprews

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, users can avoid installing the xeprews package by checking the package name and verifying its authenticity through official sources. Additionally, using tools like Vulert can help monitor and alert for vulnerabilities in open-source packages. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The xeprews package represents a significant security threat due to its malicious code execution capabilities. Users must be vigilant in verifying package authenticity and should utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to uninstall any affected packages and replace them with legitimate alternatives.

See every vulnerability recorded for xeprews →

Share this vulnerability

FAQ

Typosquatting is a malicious practice where attackers create fake packages that closely resemble legitimate ones, often with slight misspellings or variations in the name, to trick users into installing them.

Always verify the package name, author, and repository before installation. Use trusted sources and tools like Vulert to monitor for vulnerabilities.

Uninstall the xeprews package immediately and replace it with the legitimate Express package to mitigate any potential risks.

Yes, if you have installed the xeprews package, your application may be at risk of arbitrary code execution, which can lead to data breaches or system compromise.

Vulert monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities, helping you maintain the security of your software without needing direct access to the code.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall xeprews

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback