Credential Theft Vulnerability in @brick-v2/tour Package
Summary
MAL-2026-17719: Malicious code in @brick-v2/tour (npm). Affects @brick-v2/tour 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/tour package is an npm module designed to provide Angular-style functionalities, including logging capabilities. However, it has been identified as containing malicious code that executes a native addon to steal sensitive credentials from the environment. This vulnerability poses a significant risk to users who install or use the package, as it can lead to unauthorized access to sensitive information.
Vulnerability Detail
The vulnerability originates from a malicious implementation within the @brick-v2/tour package. The package includes a preinstall script that loads a native addon (metrics.node) which is executed during the installation process. This addon collects sensitive environment variables such as AWS credentials, GitHub tokens, and other identifiers, and sends them to a remote server (oob.s4yhii.com). The use of a no-op Angular-style interface disguises the malicious behavior, making it difficult for users to detect the threat. The implications of this vulnerability are severe, as it can lead to 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/tourIf 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, you can avoid using the @brick-v2/tour package until a secure version is released. Additionally, ensure that your environment variables are not exposed to untrusted code by using environment management tools.
Conclusion
The @brick-v2/tour package contains a serious vulnerability that can lead to credential theft. Users are advised to update or remove the package and monitor their applications for any signs of unauthorized access. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.
See every vulnerability recorded for @brick-v2/tour →
FAQ
The @brick-v2/tour package is an npm module that provides Angular-style functionalities, including logging capabilities.
The vulnerability works by executing a native addon during the installation of the package, which collects sensitive environment variables and sends them to a remote server.
If you have already installed the package, you should remove it immediately and check for any unauthorized access to your accounts.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.
To prevent such vulnerabilities, always review package dependencies, use trusted sources, and consider using tools like Vulert to monitor for vulnerabilities.
