Malicious Code Detected in bf-crc Package - Immediate Action Required

bf-crc Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15629: Malicious code in bf-crc (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 bf-crc package is a Node.js library that provides CRC (Cyclic Redundancy Check) calculations. It is commonly used in applications that require data integrity checks. However, recent findings have revealed that this package contains malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the bf-crc package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in version 0 and affects all subsequent versions, making it critical for users to 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 bf-crc

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, users can remove the bf-crc package from their dependencies until a secure version is released. This can be done by executing the following command: npm uninstall bf-crc.

Conclusion

The bf-crc package has been identified as containing malicious code, which poses serious security risks. Users are urged to take immediate action by updating or removing the package to safeguard their applications. Continuous monitoring using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for bf-crc →

Share this vulnerability

FAQ

The bf-crc package is used for performing CRC calculations, which are essential for ensuring data integrity in various applications.

The malicious code was discovered through security audits and monitoring by tools such as Amazon Inspector.

Using the compromised bf-crc package can lead to unauthorized access, data breaches, and potential exploitation of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply uploading your package-lock.json file, you can check for vulnerabilities without any installation required.

Yes, you can use Vulert's playground to continuously monitor your project for vulnerabilities. Visit Vulert Scanner to check if your application is affected.

How To Fix

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

npm uninstall bf-crc

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