Malicious Code Detected in alpharex Package - Security Alert

alpharex Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14402: Malicious code in alpharex (npm). Affected versions are not published. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The alpharex package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its features that enhance application performance and capabilities. However, it has been identified to contain malicious code that poses significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the alpharex package arises from the inclusion of malicious code that can compromise the security of applications utilizing this package. This issue was introduced in version 0 and affects all subsequent versions. The ramifications of this vulnerability can include unauthorized access to sensitive data, potential data breaches, and exploitation of the application environment by malicious actors.

How To Fix

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

npm uninstall alpharex

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 workaround, consider removing the alpharex package from your project until a secure version is released. You can do this by executing the command: npm uninstall alpharex.

Conclusion

The discovery of malicious code in the alpharex package highlights the importance of maintaining secure dependencies in software development. It is crucial for developers to regularly check for vulnerabilities and update their packages accordingly to safeguard their applications.

See every vulnerability recorded for alpharex →

Share this vulnerability

FAQ

alpharex is an npm package used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

The risks include unauthorized access to sensitive data, potential data breaches, and exploitation of the application environment.

Yes, it is recommended to update to the latest version of the alpharex package that addresses the security vulnerability.

If you cannot update the package right away, consider removing it from your project as a temporary measure to mitigate risks.

How To Fix

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

npm uninstall alpharex

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