Critical Malicious Code Vulnerability in xsstesting Package

xsstesting Updated 13 Feb 2026

Summary

13/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-893: Malicious code in xsstesting (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 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 xsstesting package is an npm library designed for testing cross-site scripting (XSS) vulnerabilities in web applications. It is commonly used by developers to ensure the security of their applications against XSS attacks. However, this package has been compromised, introducing malicious code that can severely affect any system where it is installed.

Vulnerability Detail

The vulnerability originates from the xsstesting package itself, which has been identified as containing embedded malicious code. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications are severe, as an attacker may gain complete control over the affected system, leading to potential data breaches and exploitation of the compromised environment.

How To Fix

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

npm uninstall xsstesting

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 other than removing the package entirely. Users should avoid using xsstesting until a secure version is released.

Conclusion

The xsstesting package has been compromised with malicious code, posing a significant risk to any system where it is installed. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for xsstesting →

Share this vulnerability

FAQ

You should uninstall the xsstesting package immediately and rotate any sensitive information stored on the affected system.

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

No, there is currently no patched version available for the xsstesting package.

Failing to remove the package can lead to unauthorized access to your system, data breaches, and potential exploitation by malicious actors.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

How To Fix

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

npm uninstall xsstesting

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