Which versions of selenium-stealth-helper are malicious?

The following PyPI versions of selenium-stealth-helper are flagged malicious: 1.0.0, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4. Treat any of these as compromised.

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

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

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

Yes — selenium-stealth-helper 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-helper 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-helper (6 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-helper across your stack and pipelines.

Malicious package

selenium-stealth-helperPyPI

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

MAL-2025-191865

Immediate action

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

pip uninstall selenium-stealth-helper

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

6 flagged

1.0.01.1.01.1.11.1.21.1.31.1.4

Indicators of compromise (SHA-256)

92e5bf8b219b2a65773ac308968c1deeefd0b0218b2f32163fbd5e001815bbc8

7c2cda67d57bc0989cefaaf7d1bf288e32cbff3768347ee959619e88ade1d44c

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-helper (6 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-helper across your stack and pipelines.
If you installed it — respond
selenium-stealth-helper 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-helper 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-helper 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-helper on PyPI has been identified as a malicious package (versions 1.0.0, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4 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-helper-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