Which versions of @browserbasehq/stagehand are malicious?

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

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

@browserbasehq/stagehand 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 — how do I know if it already compromised me?

If @browserbasehq/stagehand was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Yes — @browserbasehq/stagehand is associated with the GHSA-mmp7-557c-74pq 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 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @browserbasehq/stagehand (version 3.0.4).

Malicious package

@browserbasehq/stagehandnpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@browserbasehq/stagehand is a confirmed malicious npm package (MAL-2025-191198) that steals credentials and exfiltrates sensitive data (malicious version 3.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @browserbasehq/stagehand (npm)

MAL-2025-191198

Immediate action

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

npm uninstall @browserbasehq/stagehand

What this malware does

The package @browserbasehq/stagehand 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

3.0.4

Indicators of compromise (SHA-256)

18a4a53eddc33c2b49c9dd6b6c736bcaf6784ad6370e235aaf1fcb1a91ffa162

399bf53eafd72c4e503b750888756dfb1bd9c9e16872c9ba463458b2e76a9487

0147cee6c903a9fd8dabfedd42c60df91437e6a7a750bebff3c26ce687d4443a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @browserbasehq/stagehand (version 3.0.4).
If you installed it — respond
@browserbasehq/stagehand 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 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

GHSA-mmp7-557c-74pq

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @browserbasehq/stagehand-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

Explore

All malware advisories How O3 detects malware Vulnerability database