Malicious Code Detected in Fuze-Node Package - MAL-2025-21089

fuze-node Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21089: Malicious code in fuze-node (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

Fuze-node is an npm package designed to facilitate various functionalities in Node.js applications. It is utilized for its ease of integration and performance enhancements. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the fuze-node package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may allow unauthorized access, data breaches, or other harmful activities. The issue was introduced in version 0 and affects all subsequent versions. Users of this package should be aware of the potential ramifications, including data loss and system integrity issues.

How To Fix

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

npm uninstall fuze-node

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 temporary measure, consider removing the fuze-node package from your project until a secure version is available. You can do this by executing 'npm uninstall fuze-node' in your terminal.

Conclusion

The fuze-node package has been found to contain malicious code, posing a significant security risk to applications. Users are strongly encouraged to update to the latest version or remove the package until a secure version is available. Regular monitoring of dependencies is crucial to maintain application security.

See every vulnerability recorded for fuze-node →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and compromise application security.

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

Yes, users are advised to update to the latest version of fuze-node to mitigate the risk associated with this vulnerability.

As a workaround, consider uninstalling the fuze-node package until a secure version is available.

The vulnerability was identified by Amazon Inspector, a security tool that helps in detecting vulnerabilities in software packages.

How To Fix

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

npm uninstall fuze-node

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