Which versions of seleniumwebdriver are malicious?

The following PyPI versions of seleniumwebdriver are flagged malicious: 0.1.0, 0.1.1, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7. Treat any of these as compromised.

How do I remediate seleniumwebdriver if I installed it?

Remove seleniumwebdriver from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed seleniumwebdriver — how do I know if it already compromised me?

If seleniumwebdriver was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is seleniumwebdriver part of a known attack campaign?

Yes — seleniumwebdriver is associated with the RLMA-2024-04783, RLUA-2024-09247 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 seleniumwebdriver across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for seleniumwebdriver (7 malicious versions).

Malicious package

seleniumwebdriverPyPI

seleniumwebdriver is a confirmed malicious PyPI package (MAL-2024-5982) that executes malicious code on install (malicious versions 0.1.0, 0.1.1, 0.1.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in seleniumwebdriver (PyPI)

MAL-2024-5982

Immediate action

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

pip uninstall seleniumwebdriver

Malicious versions

7 flagged

0.1.00.1.10.1.30.1.40.1.50.1.60.1.7

Indicators of compromise (SHA-256)

0b2a1265325433af1755533755de5f45ce4172dfca80b317dc083774dcd56cd8

2a9d07661a212150660a62b2c35219a40c7f9cf1e39e0bd03347d2c1b3cf96e2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for seleniumwebdriver (7 malicious versions).
If you installed it — respond
Remove seleniumwebdriver from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If seleniumwebdriver was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. seleniumwebdriver on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04783RLUA-2024-09247

References

research.jfrog.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks seleniumwebdriver-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database