Critical Malicious Code Vulnerability in @browserbasehq/stagehand-docs Package

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191199: Malicious code in @browserbasehq/stagehand-docs (npm). Affects @browserbasehq/stagehand-docs versions 1.0.1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @browserbasehq/stagehand-docs package is an npm library designed for documentation and stage management in web applications. It provides developers with tools to create and manage documentation effectively. However, this package has been compromised, making it a significant security risk for any system that has it installed.

Vulnerability Detail

The vulnerability stems from a malicious code injection 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 may establish persistence through GitHub actions and has the potential to destroy the user's home directory. Any system with this package installed is considered fully compromised, necessitating immediate action.

How To Fix

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

npm uninstall @browserbasehq/stagehand-docs

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure that your system is monitored for any residual malicious software that may remain after the package is uninstalled.

Conclusion

The @browserbasehq/stagehand-docs package has been compromised by a malicious worm, posing a severe risk to any systems using it. Immediate removal of the package and rotation of any stored credentials are essential to mitigate the threat. Continuous monitoring for vulnerabilities is recommended.

See every vulnerability recorded for @browserbasehq/stagehand-docs →

Share this vulnerability

FAQ

Immediately uninstall the package using npm uninstall @browserbasehq/stagehand-docs and rotate any secrets or keys stored on the affected system.

The malicious code can steal sensitive tokens and credentials, propagate to other npm packages, and potentially destroy your home directory.

No, there is currently no patched version available for the @browserbasehq/stagehand-docs package. The only solution is to uninstall it.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup at Vulert Scanner.

If not addressed, this vulnerability could lead to unauthorized access to your systems, loss of sensitive data, and potential damage to your development environment.

How To Fix

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

npm uninstall @browserbasehq/stagehand-docs

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