Critical Malicious Code Vulnerability in efruitmaliciousxmlparser Package

efruitmaliciousxmlparser Updated 12 Dec 2025

Summary

12/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192548: Malicious code in efruitmaliciousxmlparser (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 efruitmaliciousxmlparser 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, posing a significant security risk to any system where it is installed. Users of this package should be aware of its potential to compromise sensitive information and system integrity.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the efruitmaliciousxmlparser package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package being flagged as malicious by security researchers, specifically noted in the GHSA report. The ramifications include potential data breaches and loss of control over the affected systems, making it critical for users to take immediate action.

How To Fix

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

npm uninstall efruitmaliciousxmlparser

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. Ensure that you monitor your system for any signs of compromise after removal.

Conclusion

The efruitmaliciousxmlparser package poses a severe security threat due to embedded malicious code. Users must take immediate action to uninstall the package and secure their systems. Regular monitoring and using tools like Vulert can help in identifying vulnerabilities in open-source packages.

See every vulnerability recorded for efruitmaliciousxmlparser →

Share this vulnerability

FAQ

Immediately uninstall the package using npm uninstall efruitmaliciousxmlparser and rotate any sensitive information stored on the affected machine.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.

Failure to remove the package could lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

The only effective mitigation is to remove the package entirely, as there are no safe alternatives or patches available.

It is advisable to review the security status of other packages from the same source and consider using trusted alternatives.

How To Fix

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

npm uninstall efruitmaliciousxmlparser

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