Malicious Code Detected in brick-node Package - MAL-2025-16165
Summary
MAL-2025-16165: Malicious code in brick-node (npm). Affected versions are not published. 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-node package is an npm library designed for various functionalities within Node.js applications. It is commonly used for its ease of integration and utility features. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that utilize it.
Vulnerability Detail
The vulnerability in the brick-node package stems 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 even complete system takeover. The issue was introduced in version 0 of the package and remains unaddressed in subsequent releases, making it critical 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 brick-nodeIf 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, consider removing the brick-node package from your project until a secure version is released. You can do this by executing: npm uninstall brick-node. This will help mitigate the risk of exposure to the malicious code.
Conclusion
The discovery of malicious code in the brick-node package highlights the importance of regularly monitoring and updating dependencies in software projects. Users must take immediate action to protect their applications by updating or removing the affected package.
See every vulnerability recorded for brick-node →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data and system resources.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Currently, there is no patched version available. Users are advised to uninstall the package until further notice.
If removal is not an option, ensure that your application has additional security measures in place to mitigate potential risks.
Utilize tools like Vulert to monitor your package-lock.json file for real-time alerts on vulnerabilities.
