Which versions of @browserbasehq/bb9 are malicious?

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

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

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

If @browserbasehq/bb9 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/bb9 part of a known attack campaign?

Yes — @browserbasehq/bb9 is associated with the GHSA-xxg4-p932-cqpg 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/bb9 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @browserbasehq/bb9 (version 1.2.21).

Malicious package

@browserbasehq/bb9npm

Advisory published Nov 25, 2025Updated Mar 2, 2026

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

Malicious code in @browserbasehq/bb9 (npm)

MAL-2025-191193

Immediate action

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

npm uninstall @browserbasehq/bb9

What this malware does

The package @browserbasehq/bb9 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.2.21

Indicators of compromise (SHA-256)

7a9a9327815902f2ad8214dd205b1c01069d6b417bafbb8c99918faae2ee1193

621961f6bd46631333873a8216c1bcc7c854e5dc3d35b70a18b8b59220e9ceec

fc1cd2b73fffb169a779067cb1753b525b3f8112141a253d64a4fb91cb0d4742

770bb82d03e2bb4aaa2bedff1846a37bec851b6fe88fdf645df92cf640a400b0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @browserbasehq/bb9 (version 1.2.21).
If you installed it — respond
@browserbasehq/bb9 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/bb9 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/bb9 on npm has been identified as a malicious package (version 1.2.21 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xxg4-p932-cqpg

References

Credits

Amazon Inspector · finder

Detect & block this

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