Critical Malicious Code Vulnerability in fruit-malicious-xml-parser Package

fruit-malicious-xml-parser Updated 12 Dec 2025

Summary

12/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192550: Malicious code in fruit-malicious-xml-parser (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The fruit-malicious-xml-parser is an npm package designed for parsing XML data. While it may offer useful functionality for developers, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk as it can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the fruit-malicious-xml-parser package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control and access sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it contains embedded malicious code that can lead to severe security breaches.

How To Fix

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

npm uninstall fruit-malicious-xml-parser

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. It is essential to monitor your system for any signs of compromise and take necessary actions to secure your environment.

Conclusion

The fruit-malicious-xml-parser package poses a severe security risk due to the presence of malicious code. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring of your applications for vulnerabilities is essential to maintain security.

See every vulnerability recorded for fruit-malicious-xml-parser →

Share this vulnerability

FAQ

It is an npm package designed for parsing XML data, but it has been compromised with malicious code.

The malicious code can grant attackers full control over your system, potentially leading to data breaches and loss of sensitive information.

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

No, there is currently no patched version available for the fruit-malicious-xml-parser package.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall fruit-malicious-xml-parser

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