Malicious Code Vulnerability in ctf2libxmljs2 Package

ctf2libxmljs2 Updated 02 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191571: Malicious code in ctf2libxmljs2 (npm). Affects ctf2libxmljs2 versions 0.30.2. 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

ctf2libxmljs2 is an npm package designed for XML parsing and manipulation in JavaScript applications. It provides developers with a set of tools to easily handle XML data structures. However, this package has been identified to contain malicious code, which poses a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in ctf2libxmljs2 stems from the inclusion of malicious code that can compromise the integrity of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was reported by ReversingLabs, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall ctf2libxmljs2

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, you can remove the ctf2libxmljs2 package from your project until a secure version is released. You can do this by running the following command: npm uninstall ctf2libxmljs2.

Conclusion

The ctf2libxmljs2 package has been identified to contain malicious code, posing a serious threat to applications that utilize it. It is crucial to update the package to a secure version or remove it until a fix is available. Regular monitoring of dependencies using tools like Vulert can help maintain application security.

See every vulnerability recorded for ctf2libxmljs2 →

Share this vulnerability

FAQ

ctf2libxmljs2 is used for parsing and manipulating XML data in JavaScript applications.

You can use Vulert to monitor your application for vulnerabilities by analyzing your package-lock.json file. Visit Vulert Scanner to check for any affected packages.

If an immediate update is not possible, consider removing the package from your project as a temporary measure until a secure version is available.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat intelligence.

Yes, using tools like Vulert, you can automate the monitoring of your open-source dependencies for vulnerabilities without needing to access the code directly.

How To Fix

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

npm uninstall ctf2libxmljs2

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.