Which versions of browser-run are malicious?

The following PyPI versions of browser-run are flagged malicious: 0.1.0, 0.2.0, 0.3.0. Treat any of these as compromised.

How do I remediate browser-run if I installed it?

browser-run 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 browser-run — how do I know if it already compromised me?

If browser-run 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 browser-run part of a known attack campaign?

Yes — browser-run is associated with the 2025-08-browser-run 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 browser-run 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 browser-run (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging browser-run across your stack and pipelines.

Malicious package

browser-runPyPI

Malicious code in browser-run (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191696

Immediate action

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

pip uninstall browser-run

What this malware does

Package uses the name as popular NPM package (https://www.npmjs.com/package/browser-run), but the only thing it does is adding a hardcoded public SSH key and then calling back. This may allow the threat actor to remotely access the machine.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-08-browser-run

Reasons (based on the campaign):

backdoor
dependency-confusion
action-hidden-in-lib-usage

Malicious versions

3 flagged

0.1.00.2.00.3.0

Indicators of compromise (SHA-256)

2cf8be6641fd96523c535fa60b1e795826587df33aeb93952a02a3cfa6061c35

3b45aebce3647704ac54d30a38e86493e0246f9ea44131394f84628656ef00ed

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 browser-run (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging browser-run across your stack and pipelines.
If you installed it — respond
browser-run 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 browser-run 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 browser-run 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. browser-run on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0, 0.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-08-browser-run

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks browser-run-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