Critical Malicious Code Vulnerability in @brick-v2/form Package
Summary
MAL-2026-17716: Malicious code in @brick-v2/form (npm). Affects @brick-v2/form versions 999.0.1 – 999.0.3. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @brick-v2/form package is an npm library designed for form handling in JavaScript applications. It is intended to provide developers with tools to manage form data efficiently. However, this package has been compromised, leading to a significant security vulnerability that exposes sensitive information.
Vulnerability Detail
The vulnerability originates from a malicious code embedded within the package. Upon loading, the package's JavaScript stub requires a compiled native addon that silently exfiltrates sensitive environment variables such as AWS credentials and GitHub tokens. This data is sent to a hardcoded external server, posing severe risks of credential theft and unauthorized access to user accounts and services.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @brick-v2/form
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, avoid using the @brick-v2/form package until a secure version is released. You can also manually remove the package from your project by running: npm uninstall @brick-v2/form.
Conclusion
The @brick-v2/form package has a critical vulnerability that allows malicious code to exfiltrate sensitive information. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications.
See every vulnerability recorded for @brick-v2/form →
FAQ
The vulnerability involves malicious code that exfiltrates sensitive environment variables to an external server.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
If you have used the affected package, uninstall it immediately and monitor your environment for any unauthorized access or credential misuse.
Check the package repository for any updates or patches. If a patched version is available, update your package using npm update @brick-v2/form.
The risks include unauthorized access to sensitive information, potential data breaches, and compromised user accounts due to exposed credentials.