Critical Malicious Code Vulnerability in ffruitmaliciousxmlparser Package

ffruitmaliciousxmlparser Updated 12 Dec 2025

Summary

12/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192549: Malicious code in ffruitmaliciousxmlparser (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 ffruitmaliciousxmlparser package is an npm library designed for parsing XML data. It is often used in applications that require XML data manipulation and processing. However, this package has been identified as containing malicious code, which poses a significant security risk to any system that has it installed. The malicious nature of the code can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the ffruitmaliciousxmlparser package. This code can compromise the integrity of the host system, allowing attackers to gain full control over it. The origin of this vulnerability is linked to the package being intentionally designed to include harmful functionalities. The ramifications of this vulnerability are severe, as it can lead to data breaches, loss of sensitive information, and unauthorized actions performed on behalf of the user.

How To Fix

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

npm uninstall ffruitmaliciousxmlparser

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 all secrets and keys stored on the affected computer are rotated immediately from a different, secure computer. This step is essential to mitigate any potential damage caused by the malicious code.

Conclusion

The ffruitmaliciousxmlparser package contains malicious code that poses a serious threat to any system using it. Immediate removal of the package is necessary to prevent unauthorized access and control. Users should also rotate any sensitive information stored on affected systems and consider using tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for ffruitmaliciousxmlparser →

Share this vulnerability

FAQ

ffruitmaliciousxmlparser is an npm package used for parsing XML data in applications.

If you have the ffruitmaliciousxmlparser package installed, your system is considered compromised. You should take immediate action to secure your system.

You should remove the ffruitmaliciousxmlparser package from your project and replace it with a secure alternative.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

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

How To Fix

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

npm uninstall ffruitmaliciousxmlparser

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