Critical Malicious Code Vulnerability in fleebee Package

fleebee Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20694: Malicious code in fleebee (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 fleebee package is an npm library designed for [insert functionality here, e.g., managing user sessions, data processing, etc.]. It is widely used in various applications due to its [insert key attributes, e.g., ease of use, flexibility, etc.]. However, recent findings have revealed that the package contains malicious code, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the fleebee package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability affects all versions starting from 0, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall fleebee

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 workaround, you can remove the fleebee package from your project by running the following command: npm uninstall fleebee. This will prevent the execution of the malicious code until a secure version is released.

Conclusion

The discovery of malicious code within the fleebee package poses a serious threat to users and their applications. It is crucial to take immediate action by updating or removing the package to mitigate potential risks. Utilizing tools like Vulert can help monitor for vulnerabilities and ensure the security of your software.

See every vulnerability recorded for fleebee →

Share this vulnerability

FAQ

The fleebee package is used for [insert specific functionality], making it a popular choice among developers.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can access the Vulert playground at Vulert Scanner without any signup.

If you cannot update the package, it is advisable to uninstall it temporarily to avoid any security risks associated with the malicious code.

Yes, you can use Vulert to monitor your application for vulnerabilities by simply using your package-lock.json file.

Failing to address this vulnerability could lead to unauthorized access, data breaches, and other security incidents that could severely impact your application and its users.

How To Fix

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

npm uninstall fleebee

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