Critical Malicious Code Vulnerability in gfruitmaliciousxmlparser Package

gfruitmaliciousxmlparser Updated 12 Dec 2025

Summary

12/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192551: Malicious code in gfruitmaliciousxmlparser (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The gfruitmaliciousxmlparser package is an npm library designed for parsing XML data. It is intended to facilitate the handling of XML files within JavaScript applications. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed. Users of this package should be aware of its potential to compromise sensitive data and system integrity.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the gfruitmaliciousxmlparser package. This code can fully compromise any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems. The malicious nature of the code is classified under CWE-506, indicating that it contains code that appears to be harmful.

How To Fix

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

npm uninstall gfruitmaliciousxmlparser

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

Currently, there are no effective workarounds to mitigate the risks posed by this malicious package. The only recommended action is to uninstall the package entirely.

Conclusion

The gfruitmaliciousxmlparser package poses a critical security risk due to the presence of malicious code. Immediate action is required to remove the package and secure any compromised information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their dependencies.

See every vulnerability recorded for gfruitmaliciousxmlparser →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information that may have been compromised.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities. Visit Vulert Scanner to check your application without any signup.

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

Keeping this package installed can lead to unauthorized access to sensitive data and complete system compromise.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time.

How To Fix

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

npm uninstall gfruitmaliciousxmlparser

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