Which versions of multithreadedexecution are malicious?

The following PyPI versions of multithreadedexecution are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate multithreadedexecution if I installed it?

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

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

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

Malicious package

multithreadedexecutionPyPI

Malicious code in multithreadedexecution (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191798

Immediate action

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

pip uninstall multithreadedexecution

What this malware does

Once run, package downloads and installs an infostealer

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

Campaign: 2025-11-discord-selfsbotsx

Reasons (based on the campaign):

Downloads and executes a remote executable.
infostealer
malware
peristence-autorun

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5af5a526d3255cf6c76e0490269ba46e56c0944a8f7c761e63ee801f07ffd1d0

3248950b032e1381ddc79d43dfdba8fb6dccce4b1afafd5825e560d793b3bd09

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

Campaign

2025-11-discord-selfsbotsx

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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