Which versions of python-module-installer are malicious?

The following PyPI versions of python-module-installer are flagged malicious: 3.15.6, 3.15.7, 3.15.8, 3.15.9, 3.15.10. Treat any of these as compromised.

How do I remediate python-module-installer if I installed it?

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

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

Yes — python-module-installer is associated with the 2026-03-old-python-module-installer 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 python-module-installer 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 python-module-installer (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-module-installer across your stack and pipelines.

Malicious package

python-module-installerPyPI

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

MAL-2026-1263

Immediate action

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

pip uninstall python-module-installer

What this malware does

The package clones a legitimate webdavclient3 library and modifies it to be an installer utility. During installation, the package exfiltrates the current working directory to a remote WebDAV server or Telegram Bot. Additionally, the package targets cryptocurrency operations in another suspicious project, https://github.com/fewcatltd/zkSync/

The install_modules() method injects code into two files, which are characteristic for this repository, and causes exfiltrating configuration files during cryptocurrency exchange operations.

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

Campaign: 2026-03-old-python-module-installer

Reasons (based on the campaign):

impersonation
dependency-confusion
files-exfiltration
action-hidden-in-lib-usage
clones-real-package
crypto-related
exfiltration-crypto

Malicious versions

5 flagged

3.15.63.15.73.15.83.15.93.15.10

Indicators of compromise (SHA-256)

61bfa181c5afb9e33e0d529138c813fc05d8130062182d9d1a5cb4ef9c8da0ea

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

Campaign

2026-03-old-python-module-installer

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks python-module-installer-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