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)
What this malware does
The package's setup.py overrides the install and develop cmdclass to base64-decode a bundled request/.payload file and launch it via subprocess.Popen([sys.executable, '-c', payload],...) with DETACHED_PROCESS|CREATE_NO_WINDOW at pip install time. The decoded payload is a Windows infostealer that enumerates Chrome/Edge/Brave/Opera/Vivaldi/Firefox profiles (cookies, logins, key4.db, autofill, saved cards), 50+ crypto wallet browser extensions and standalone wallet apps (Electrum, Binance, Ethereum), clipboard contents, email/FTP client credentials, and system fingerprint data, advertising a Chrome v20 ABE bypass. Collected data is exfiltrated to api.telegram.org/bot<TOKEN>/sendMessage and /sendDocument, and to https://recloud-blush.vercel.app; ipinfo.io is queried for geolocation. The payload also installs boot persistence disguised as svchost.exe, performs periodic screenshotting when crypto apps are active, targeted keylogging for passwords/seeds/private keys, and maintains a real-time C2 channel. The package name typosquats 'multiprocessing' while its metadata forges the publisher identity as 'Python Software Foundation' ([email protected], github.com/psf/request) and request/init.py re-exports symbols from the real requests library as a cover story.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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
Campaign
References
Credits
- Amazon Inspector · finder
- 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.