Critical Malicious Code Vulnerability in dfruitmaliciousxmlparser Package

dfruitmaliciousxmlparser Updated 12 Dec 2025

Summary

12/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192547: Malicious code in dfruitmaliciousxmlparser (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 dfruitmaliciousxmlparser 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 risk to any system that has it installed. The presence of such code can lead to unauthorized access and compromise of sensitive information.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the dfruitmaliciousxmlparser package. This code can fully compromise any computer that has the package installed, allowing external entities to gain control over the system. The ramifications include potential data breaches, unauthorized access to secrets and keys, and the installation of additional malicious software. The vulnerability is classified under CWE-506, indicating that the product contains embedded malicious code.

How To Fix

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

npm uninstall dfruitmaliciousxmlparser

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 to mitigate the risks associated with this vulnerability. The only recommended action is to remove the package entirely from your system.

Conclusion

The dfruitmaliciousxmlparser package contains malicious code that poses a severe risk to any system where it is installed. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring vulnerabilities in your applications.

See every vulnerability recorded for dfruitmaliciousxmlparser →

Share this vulnerability

FAQ

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

You can use the Vulert platform to monitor and alert for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Keeping this package can lead to unauthorized access to your system, data breaches, and potential installation of additional malicious software.

No, there is currently no patched version available for this package. The only solution is to uninstall it.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, providing a proactive approach to security.

How To Fix

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

npm uninstall dfruitmaliciousxmlparser

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