Which versions of sklearns are malicious?

The following PyPI versions of sklearns are flagged malicious: 0.3. Treat any of these as compromised.

How do I remediate sklearns if I installed it?

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

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

Yes — sklearns is associated with the RLMA-2024-11166, GENERIC-standard-pypi-install-pentest, RLUA-2026-00762 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 sklearns 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 sklearns (version 0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sklearns across your stack and pipelines.

Malicious package

sklearnsPyPI

Malicious code in sklearns (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11708

Immediate action

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

pip uninstall sklearns

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.3

Indicators of compromise (SHA-256)

b65e44dd655f4c6f4479ba4fc54e34336df0f1e4134d5e1c5fb0f45a95446762

e887bf777469970f69130d4b4c9a3ab938c4f7a93d037d06ade7be9d57079a10

4e260abb013bb5822352ea0e834c081da4d0ab7c66ac8c853cfd809552d02d1a

a9b09fddb2e713c5ca5d755dbad3da9733e5b74d153c285405c106c70b42b655

3151785db0d1ef96e47d1f58d83d08ce6971fd7f40b68aeb1cbf79df47d76067

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 sklearns (version 0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sklearns across your stack and pipelines.
If you installed it — respond
sklearns 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 sklearns 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 sklearns 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. sklearns on PyPI has been identified as a malicious package (version 0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-11166GENERIC-standard-pypi-install-pentestRLUA-2026-00762

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks sklearns-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