Which versions of browser-cookies3 are malicious?

The following PyPI versions of browser-cookies3 are flagged malicious: 1.1. Treat any of these as compromised.

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

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

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

Yes — browser-cookies3 is associated with the RLMA-2024-07894, RLUA-2025-01204, 2024-08-dirutils, RLUA-2026-00157 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-cookies3 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-cookies3 (version 1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging browser-cookies3 across your stack and pipelines.

Malicious package

browser-cookies3PyPI

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

MAL-2024-9952

Immediate action

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

pip uninstall browser-cookies3

What this malware does

Package contains a compiled infostealer that is started instead of promised functionality

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

Campaign: 2024-08-dirutils

Reasons (based on the campaign):

infostealer

Malicious versions

1 flagged

1.1

Indicators of compromise (SHA-256)

1fd16f1c8b35abebeb1e90e2f461276f7b43d5e79d3eda77a51cb7c40f3115d3

8ec9f52bcc3a58243396d77c8396cb930e08c25523c8b78dea7c68a2307f6651

4529ee7157c7665fecc2f4b527ed7f938377f6599c082e8c3fe86593dc37afff

ac253e47b0fa143074f6239c3c84b3ecd3521d37f71c4f92937f53cafc5067b5

6aa5796d9bc82229c0f0364579db2d44619ec9869ed1e665d1cb9692112808db

1e558f0477c72bd84d2c0899491448bef0c2df923689840e2a9993e96842010f

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

Campaign

RLMA-2024-07894RLUA-2025-012042024-08-dirutilsRLUA-2026-00157

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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