Critical Malicious Code Vulnerability in @browserbasehq/director-ai Package
Summary
MAL-2025-191194: Malicious code in @browserbasehq/director-ai (npm). Affects @browserbasehq/director-ai versions 1.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 @browserbasehq/director-ai package is an npm library designed for managing AI-driven browser functionalities. It is utilized in various web applications to enhance user experience through intelligent interactions. However, this package has been compromised, leading to significant security risks for any system utilizing it.
Vulnerability Detail
The vulnerability originates from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing tokens and credentials, publishing them to GitHub, and propagating itself to other npm packages owned by the user. Additionally, it can establish persistence through GitHub actions and may even destroy the user's home directory. Any system with this package installed is considered fully compromised, necessitating immediate action to secure sensitive information.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @browserbasehq/director-aiIf 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
Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package and rotating all secrets and keys stored on the affected system.
Conclusion
The @browserbasehq/director-ai package has been compromised, posing severe security risks to any system using it. Immediate removal of the package and rotation of sensitive credentials are essential steps to mitigate the impact of this vulnerability. Regular monitoring and auditing of dependencies are recommended to maintain security.
See every vulnerability recorded for @browserbasehq/director-ai →
FAQ
Immediately remove the package and rotate all sensitive credentials stored on your system.
The payload can steal sensitive tokens and credentials, potentially leading to unauthorized access to your accounts and data.
While many npm packages are safe, it is essential to monitor and audit your dependencies regularly to ensure they are not compromised.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.
Regularly update your packages, audit dependencies, and use tools like Vulert to monitor for vulnerabilities.
