What does the multyproccess malware do?

During installation, package executes an infostealer that e.g. exfiltrates browsers and crypto wallets data, establishes persistence, monitors clipboard. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2026-08-multyproccess Reasons (based on the campaign): - typosquatting - infostealer - exfiltration-crypto - exfiltration-browser-data - clones-real-package - The package overrides the install command in setup.py to execute malicious code during installation. - The package contains code to detect if it is running in a sandbox environment. - obfuscation - persistence

Which versions of multyproccess are malicious?

The following PyPI versions of multyproccess are flagged malicious: 2.32.3, 2.32.4, 2.32.5, 2.32.6. Treat any of these as compromised.

How do I remediate multyproccess if I installed it?

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

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

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

Malicious package

multyproccessPyPI

multyproccess is a confirmed malicious PyPI package (MAL-2026-14401) that steals credentials and exfiltrates sensitive data (malicious versions 2.32.3, 2.32.4, 2.32.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in multyproccess (PyPI)

MAL-2026-14401

Immediate action

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

pip uninstall multyproccess

What this malware does

During installation, package executes an infostealer that e.g. exfiltrates browsers and crypto wallets data, establishes persistence, monitors clipboard.

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

Campaign: 2026-08-multyproccess

Reasons (based on the campaign):

typosquatting
infostealer
exfiltration-crypto
exfiltration-browser-data
clones-real-package
The package overrides the install command in setup.py to execute malicious code during installation.
The package contains code to detect if it is running in a sandbox environment.
obfuscation
persistence

Malicious versions

4 flagged

2.32.32.32.42.32.52.32.6

Indicators of compromise (SHA-256)

93a751dcfb2e5ac6058cbd62220d237288d3ceb4d8fe152b7ef7babb645df660

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

Campaign

2026-08-multyproccess

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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