Critical Malicious Code Vulnerability in bee-quarl Package

bee-quarl Updated 02 Mar 2026

Summary

02/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1103: Malicious code in bee-quarl (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 bee-quarl package is an npm library that is used for various functionalities within JavaScript applications. It is designed to facilitate certain tasks but has been compromised, leading to significant security concerns. The package's malicious nature poses a risk to any system that has it installed, potentially allowing unauthorized access and control over sensitive data.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the bee-quarl package. This code can fully compromise any computer that has the package installed, leading to unauthorized access to secrets and keys stored on that system. The origin of this issue is linked to the package being flagged as malicious by security researchers, indicating that it may have been intentionally designed to exploit users. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall bee-quarl

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 the bee-quarl package. The best course of action is to uninstall the package and secure your system.

Conclusion

The bee-quarl package presents a critical security vulnerability due to embedded malicious code. Immediate action is required to uninstall the package and secure any affected systems. Regular monitoring of dependencies using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for bee-quarl →

Share this vulnerability

FAQ

bee-quarl is an npm package used in JavaScript applications, but it has been compromised with malicious code.

If you have the bee-quarl package installed, your system is considered compromised. You should take immediate action to remove it.

After uninstalling, rotate all secrets and keys stored on the affected system from a secure computer.

No, there is currently no patched version of the bee-quarl package available.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.

How To Fix

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

npm uninstall bee-quarl

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