Critical Malicious Code Vulnerability in freedom-baileys Package

freedom-baileys Updated 06 Feb 2026

Summary

03/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-674: Malicious code in freedom-baileys (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 freedom-baileys package is a Node.js library commonly used in various applications for its functionality in handling specific tasks related to data processing and manipulation. However, it has been identified as containing malicious code, making it a significant security risk for any system utilizing it. The presence of this vulnerability can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the freedom-baileys package, as reported by sources such as Amazon Inspector and GHSA. This code can compromise any computer that has the package installed, allowing attackers to gain full control over the system. The malicious code can potentially expose sensitive information, including secrets and keys, leading to severe security breaches. Users are advised to treat any system running this package as compromised and take immediate action to mitigate risks.

How To Fix

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

npm uninstall freedom-baileys

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 workaround, ensure that all secrets and keys stored on the affected computer are rotated immediately from a different, secure computer. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The freedom-baileys package has been identified as containing malicious code, posing a significant security risk. Users must take immediate action to remove the package and secure their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for freedom-baileys →

Share this vulnerability

FAQ

Freedom-baileys is a Node.js library used for data processing and manipulation tasks in various applications.

If you have the freedom-baileys package installed, your system is likely compromised. Use tools like Vulert to check for vulnerabilities.

Immediately remove the freedom-baileys package and rotate any sensitive information stored on the affected system.

Currently, there is no patched version available. Users are advised to remove the package entirely.

Vulert monitors and alerts for open-source vulnerabilities in your software using just package-lock.json, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall freedom-baileys

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