Which versions of python3-shodan are malicious?

The following PyPI versions of python3-shodan are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate python3-shodan if I installed it?

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

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

Yes — python3-shodan is associated with the 2025-05-sl4x01 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 python3-shodan 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 python3-shodan (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python3-shodan across your stack and pipelines.

Malicious package

python3-shodanPyPI

Malicious code in python3-shodan (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191845

Immediate action

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

pip uninstall python3-shodan

What this malware does

Packages that seem to be created by a legit bug bounty hunter. Designed to look like created by different organisations, they contain a couple of data exfiltration (including all env variables) and potential remote code execution (though the URL seems not to serve any code).

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

Campaign: 2025-05-sl4x01

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.
exfiltration-env-variables
impersonation

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

422f6521d87f0b265b70862fad840f74d262b48235a70e6db133fa55fa783cfa

b4fca245262ff8de532efc88e1941697e6994786e09eca8a9cbcdbf9faff5cca

cffb4935106ce0254db0bb29a553a83006e1bfd48324219984b910041877b0b0

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

Campaign

2025-05-sl4x01

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks python3-shodan-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