Critical Malicious Code Vulnerability in fizzler Package

fizzler Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20631: Malicious code in fizzler (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 fizzler package is an npm library designed for various functionalities, including data manipulation and processing. It is widely used in JavaScript applications for its ease of integration and utility features. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the fizzler package, which was introduced in version 0. This code can potentially compromise the security of applications, leading to unauthorized access, data breaches, or other malicious activities. The presence of such code can severely impact the integrity and confidentiality of user data.

How To Fix

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

npm uninstall fizzler

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, you can remove the fizzler package from your project until a secure version is available. Use the following command to uninstall it: npm uninstall fizzler.

Conclusion

The fizzler package has been identified to contain malicious code, posing significant risks to applications that utilize it. It is crucial to update to the latest patched version or uninstall the package to ensure the security of your application. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for fizzler →

Share this vulnerability

FAQ

The fizzler package is an npm library used for data manipulation and processing in JavaScript applications.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

The malicious code can lead to unauthorized access, data breaches, and other security incidents that compromise user data and application integrity.

Yes, a patched version of the fizzler package is available. You should update to the latest version to mitigate the risk.

If immediate updates are not possible, consider uninstalling the fizzler package as a temporary workaround until a secure version can be implemented.

How To Fix

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

npm uninstall fizzler

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