Critical Malicious Code Vulnerability in xvxx Package

xvxx Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192656: Malicious code in xvxx (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 xvxx package is an npm library that is used for various functionalities in JavaScript applications. It is designed to facilitate certain tasks within the development environment. However, this package has been identified as containing malicious code that compromises the security of any system where it is installed, leading to potential unauthorized access and data breaches.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the xvxx package. This code can fully compromise any computer that has the package installed, allowing an outside entity to gain control over the system. Users are advised to treat any system with this package as compromised, as it may lead to unauthorized access to sensitive information, including secrets and keys stored on the device.

How To Fix

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

npm uninstall xvxx

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

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the xvxx package completely and secure your system.

Conclusion

The xvxx package has been identified as containing malicious code that compromises the security of any system it is installed on. Immediate action is required to uninstall the package and secure sensitive information. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for xvxx →

Share this vulnerability

FAQ

You should immediately uninstall the xvxx package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Keeping the xvxx package installed poses significant risks, including unauthorized access to your system and potential data breaches.

While removing the package is essential, it is also crucial to rotate all secrets and keys as there is no guarantee that removing the package will eliminate all malicious software.

Regularly monitor your dependencies using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

How To Fix

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

npm uninstall xvxx

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