Which versions of @browserbasehq/stagehand-docs are malicious?

The following npm versions of @browserbasehq/stagehand-docs are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate @browserbasehq/stagehand-docs if I installed it?

@browserbasehq/stagehand-docs is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @browserbasehq/stagehand-docs — how do I know if it already compromised me?

If @browserbasehq/stagehand-docs was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @browserbasehq/stagehand-docs part of a known attack campaign?

Yes — @browserbasehq/stagehand-docs is associated with the GHSA-4rjx-92xj-8cj8 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @browserbasehq/stagehand-docs across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @browserbasehq/stagehand-docs (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @browserbasehq/stagehand-docs across your stack and pipelines.

Malicious package

@browserbasehq/stagehand-docsnpm

Malicious code in @browserbasehq/stagehand-docs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191199

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @browserbasehq/stagehand-docs

What this malware does

The package @browserbasehq/stagehand-docs was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

b36ff6ec1a3fbe52f5a839fafed440dcaecb20ebece8c48a56f792617e8a0cbb

a2de758cdd08db8e0cd82dfa59987632b2a05c8fef4b2891a5447ce525d0f2d0

ba1d760d2f3ab2322b527554b05f55f9d8ceb73868da963ea4d060a1a5a5134f

563730f82e49536b57e409ef31b39c37905cf5634c00a2509d4804d7255c8a3d

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @browserbasehq/stagehand-docs (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @browserbasehq/stagehand-docs across your stack and pipelines.
If you installed it — respond
@browserbasehq/stagehand-docs is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @browserbasehq/stagehand-docs was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @browserbasehq/stagehand-docs before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @browserbasehq/stagehand-docs on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4rjx-92xj-8cj8

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @browserbasehq/stagehand-docs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring