Malicious Code Detected in cbfour Package - Security Alert

cbfour Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16676: Malicious code in cbfour (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The cbfour package is an npm library designed for specific functionalities within JavaScript applications. It is commonly used for various tasks, but recent findings have revealed that it contains malicious code, posing a significant security risk to applications that utilize it. Users of cbfour should be aware of its potential vulnerabilities and take necessary precautions.

Vulnerability Detail

The vulnerability in the cbfour package originates from the inclusion of malicious code that can compromise the security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability is classified under the identifier MAL-2025-16676, and it affects all versions starting from 0.

How To Fix

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

npm uninstall cbfour

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, if you cannot update the package immediately, consider removing the cbfour package from your project until a secure version is available. You can do this by executing: npm uninstall cbfour.

Conclusion

The cbfour package has been identified as containing malicious code, which poses a serious security risk to applications that utilize it. Users are strongly advised to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for cbfour →

Share this vulnerability

FAQ

cbfour is an npm package used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

If you cannot update cbfour immediately, consider uninstalling it from your project until a secure version is released.

Using the compromised cbfour package can lead to unauthorized access to your application, potential data breaches, and other security threats.

You can use tools like Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall cbfour

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