Which versions of selenium-integration are malicious?

The following PyPI versions of selenium-integration are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate selenium-integration if I installed it?

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

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

Yes — selenium-integration is associated with the 2026-01-system-integration 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-integration across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for selenium-integration (version 1.0.1).

Malicious package

selenium-integrationPyPI

Advisory published Jan 25, 2026Updated Jan 25, 2026

selenium-integration is a confirmed malicious PyPI package (MAL-2026-506) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in selenium-integration (PyPI)

MAL-2026-506

Immediate action

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

pip uninstall selenium-integration

What this malware does

When importing the module, code downloads and executes a highly obfuscated remote script.

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

Campaign: 2026-01-system-integration

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
obfuscation

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

50120169fb4cd982eb19b5dee69b1aa881d250d6bab46aaadb2746b92f0ec158

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for selenium-integration (version 1.0.1).
If you installed it — respond
selenium-integration 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-integration 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. selenium-integration on PyPI has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-01-system-integration

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks selenium-integration-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

Explore

All malware advisories How O3 detects malware Vulnerability database