Which versions of browser-cookies1 are malicious?

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

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

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

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

Yes — browser-cookies1 is associated with the RLMA-2024-07893, 2024-08-dirutils, RLUA-2026-00156 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-cookies1 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-cookies1 (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-cookies1 across your stack and pipelines.

Malicious package

browser-cookies1PyPI

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

MAL-2024-9951

Immediate action

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

pip uninstall browser-cookies1

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)

509777ac01f9c2c48accd7534acf1a46b1b1e42545e3786e22b86ad54879e79a

0c460b56a0ff44db38f7f621f373a5f2b941d651aa5ab194d1340b5416919afe

5cabd14fc21e5314fd1778bac4e49f0cb8a145e773e147666070d85aa60e422c

45a8ff710f7cba3f30db164b6fac21bafd81a08e7e41a496b6ffb135d16d85e9

df8e5d1a6d2e9ffc9aa040d23186fd1b800b8b6edf11e535e00b41680033a302

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-cookies1 (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-cookies1 across your stack and pipelines.
If you installed it — respond
browser-cookies1 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-cookies1 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-cookies1 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-cookies1 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-078932024-08-dirutilsRLUA-2026-00156

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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