Critical Malicious Code Vulnerability in cfruitmaliciousxmlparser Package

cfruitmaliciousxmlparser Updated 12 Dec 2025

Summary

12/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192546: Malicious code in cfruitmaliciousxmlparser (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 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 cfruitmaliciousxmlparser package is an npm library designed for parsing XML data. It is intended to facilitate the handling of XML files in JavaScript applications. However, this package has been identified as containing malicious code that compromises the security of any system where it is installed. Users should be aware of its potential risks and the need for immediate action if they have this package in their projects.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the cfruitmaliciousxmlparser package. This code can lead to a complete compromise of any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code has been confirmed by security researchers, and it poses a significant risk to users who may unknowingly install or use this package in their applications.

How To Fix

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

npm uninstall cfruitmaliciousxmlparser

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 ensure that they do not rely on cfruitmaliciousxmlparser for XML parsing and look for alternative libraries that do not pose security risks.

Conclusion

The cfruitmaliciousxmlparser package poses a critical security risk due to its embedded malicious code. Immediate action is required to remove the package and secure any sensitive information. Users should seek alternative libraries for XML parsing to avoid similar vulnerabilities in the future.

See every vulnerability recorded for cfruitmaliciousxmlparser →

Share this vulnerability

FAQ

You should uninstall the package immediately using 'npm uninstall cfruitmaliciousxmlparser' 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. Visit Vulert Scanner to check your application without needing to sign up.

No, there is no patched version available for this package. The only solution is to remove it from your system.

Keeping this package installed can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Yes, consider using well-known and trusted packages such as xml2js or fast-xml-parser, which do not have known vulnerabilities.

How To Fix

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

npm uninstall cfruitmaliciousxmlparser

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