Malicious Code Detected in xpvnsulc Package - Critical Security Alert

xpvnsulc Updated 02 Oct 2025

Summary

13/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5841: Malicious code in xpvnsulc (npm). Affects xpvnsulc versions >= 50.50.50. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The xpvnsulc package is an npm library that is utilized for various functionalities within JavaScript applications. However, it has been flagged for containing malicious code that poses significant security risks. The package's primary attributes include its ease of integration and functionality, but its recent identification as malicious raises concerns about its safety for developers and users alike.

Vulnerability Detail

The vulnerability in the xpvnsulc package arises from its communication with a domain linked to malicious activities. This behavior can lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. The malicious nature of the package was identified by the OpenSSF Package Analysis project, which traced its origins to a specific version (50.50.50) that has been confirmed to exhibit harmful behavior.

How To Fix

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

npm uninstall xpvnsulc

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 an immediate workaround, consider removing the xpvnsulc package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall xpvnsulc'. Additionally, monitor your application for any unusual activity that may have resulted from the package.

Conclusion

The xpvnsulc package has been identified as malicious, posing serious security risks to applications that utilize it. Developers should take immediate action to remove the package and monitor their systems for any unusual activity. Staying informed about updates and utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for xpvnsulc →

Share this vulnerability

FAQ

The xpvnsulc package is an npm library that provides various functionalities for JavaScript applications, but it has been flagged for malicious behavior.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If you have installed the xpvnsulc package, it is recommended to uninstall it immediately and monitor your application for any suspicious activity.

Currently, there is no specific patched version mentioned. It is advisable to keep an eye on the package repository for updates.

Using the xpvnsulc package can expose your application to data breaches, unauthorized access, and exploitation due to its malicious behavior.

How To Fix

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

npm uninstall xpvnsulc

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