Which versions of search-python-common are malicious?

The following PyPI versions of search-python-common are flagged malicious: 1, 1.0, 10.0. Treat any of these as compromised.

How do I remediate search-python-common if I installed it?

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

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

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

Malicious package

search-python-commonPyPI

Malicious code in search-python-common (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11702

Immediate action

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

pip uninstall search-python-common

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

3 flagged

11.010.0

Indicators of compromise (SHA-256)

72df7f4cd461be901d0a9ec6fb3be2fa33cc09a7d7300b95dda5cf56cecb6a9f

fbaaf554f56f157b67f5e0691ff202348ef000809fafe501be6f4f17c8c0c83d

0c88a2aa7e382781b4c0032b273e3e772875f1e3cbd8e22569c90d1d3ebf9198

3f7b85bfd6f1469ef08c91e389fa36bebdf7578206c8bc93db2b249429dc2c51

bb5eb354916e4d9f17c3365f45e79ef59c390dde55a7eef9de32f194bde44b6b

0b88bdbc50c49163dd53a9e218126fe669483815cb269e26b0d27ff834e56e79

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

Campaign

RLMA-2024-11160GENERIC-standard-pypi-install-pentestRLUA-2026-00748

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks search-python-common-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