Which versions of selenium-stealth-utils are malicious?

The following PyPI versions of selenium-stealth-utils are flagged malicious: 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.5, 2.0.7, 2.0.8, 2.0.9, 2.1.0, 2.1.3, 2.1.4, 2.1.7, 2.1.8, 2.2.0. Treat any of these as compromised.

How do I remediate selenium-stealth-utils if I installed it?

selenium-stealth-utils 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 selenium-stealth-utils — how do I know if it already compromised me?

If selenium-stealth-utils 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 selenium-stealth-utils part of a known attack campaign?

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

Malicious package

selenium-stealth-utilsPyPI

Malicious code in selenium-stealth-utils (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191866

Immediate action

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

pip uninstall selenium-stealth-utils

What this malware does

During importing, a malicious executable is being downloaded and started. According to sandbox report, the executable is an infostealer of rhadamanthys family.

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

Campaign: 2025-08-selenium-stealth-helper

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
impersonation
malware

Malicious versions

14 flagged

2.0.02.0.12.0.22.0.32.0.52.0.72.0.82.0.92.1.02.1.32.1.42.1.72.1.82.2.0

Indicators of compromise (SHA-256)

0e1ba9867a070106f834254bd0935ea54cf1cf91003805a4a004227cad0115aa

b7721bb039c55a43bd1dc81dfad14494df158912f9dda006a67881ce54be64d3

4ba9e7515ba505a314fc89cbfb928ef5ce1e068c3fe93bd3ea5bac9b0b7f951e

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 selenium-stealth-utils (14 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging selenium-stealth-utils across your stack and pipelines.
If you installed it — respond
selenium-stealth-utils 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 selenium-stealth-utils 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 selenium-stealth-utils 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. selenium-stealth-utils on PyPI has been identified as a malicious package (versions 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.5, 2.0.7, 2.0.8, 2.0.9, and 6 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-08-selenium-stealth-helper

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks selenium-stealth-utils-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