Critical Malicious Code Vulnerability in @vtim/xss-poc Package

@vtim/xss-poc Updated 16 Mar 2026

Summary

16/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1440: Malicious code in @vtim/xss-poc (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 @vtim/xss-poc package is an npm library designed for testing cross-site scripting (XSS) vulnerabilities. It is intended for developers to simulate and analyze XSS attacks in a controlled environment. However, this package has been compromised, embedding malicious code that poses significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @vtim/xss-poc package. This code can fully compromise any computer that has the package installed, allowing an attacker to gain unauthorized access to sensitive information, including secrets and keys stored on the affected system. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code.

How To Fix

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

npm uninstall @vtim/xss-poc

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 workaround, ensure that your application does not rely on the @vtim/xss-poc package. If you need similar functionality, consider using alternative libraries that are known to be secure and actively maintained. Always review the security of third-party packages before installation.

Conclusion

The @vtim/xss-poc package has been identified as containing malicious code that can compromise systems. Immediate action is required to uninstall the package and secure sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @vtim/xss-poc →

Share this vulnerability

FAQ

Immediately uninstall the package using npm uninstall @vtim/xss-poc and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application by visiting the Vulert playground at Vulert Scanner without needing to sign up.

No, there is currently no patched version of the @vtim/xss-poc package available. The only solution is to uninstall it.

Keeping the package installed can lead to full compromise of your system, allowing attackers to access sensitive data and potentially control your computer.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.

How To Fix

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

npm uninstall @vtim/xss-poc

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