Which versions of @browserbasehq/sdk-functions are malicious?

The following npm versions of @browserbasehq/sdk-functions are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate @browserbasehq/sdk-functions if I installed it?

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

If @browserbasehq/sdk-functions 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.

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

Search your lockfiles and build artifacts for @browserbasehq/sdk-functions (version 0.0.4).

Malicious package

@browserbasehq/sdk-functionsnpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

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

Malicious code in @browserbasehq/sdk-functions (npm)

MAL-2025-191197

Immediate action

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

npm uninstall @browserbasehq/sdk-functions

What this malware does

The package @browserbasehq/sdk-functions was found to contain malicious code.

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

0.0.4

Indicators of compromise (SHA-256)

4db65f5859e6b50d2a6348ae3345ae90a5395eb1c39c6626bde123a38c07c103

0dcba06b8039c18710f9cd77f877d6f7bcf48e1c0d25d161f404e2a14b689fca

Detection & response playbook

Credential / info stealer

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

References

Credits

Amazon Inspector · finder

Detect & block this

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