Malicious Code Detected in braincrow Package - Security Alert

braincrow Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16065: Malicious code in braincrow (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 braincrow package is an npm library designed for various functionalities in JavaScript applications. It is utilized by developers for its features, but recent findings have revealed that it contains malicious code, posing a significant security risk to users and their applications. This vulnerability can lead to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability in the braincrow package originates from the inclusion of malicious code that can compromise the security of applications using this package. The ramifications include potential data theft, unauthorized access to user information, and exploitation of the affected systems. This issue is critical as it affects all versions of the package starting from its introduction, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall braincrow

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, consider removing the braincrow package from your project until a secure version is released. You can do this by running: npm uninstall braincrow. This will help mitigate the risk while you await a fix.

Conclusion

The discovery of malicious code in the braincrow package poses a serious threat to users and their applications. Immediate action is required to update or remove the package to safeguard against potential security breaches. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for braincrow →

Share this vulnerability

FAQ

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

The malicious code can lead to unauthorized access, data breaches, and exploitation of your application, compromising user data and security.

You should immediately update the package to the latest version or uninstall it until a secure version is released.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall braincrow

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