Which versions of threading-assistant are malicious?

The following PyPI versions of threading-assistant are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate threading-assistant if I installed it?

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

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

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

Malicious package

threading-assistantPyPI

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

MAL-2024-12363

Immediate action

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

pip uninstall threading-assistant

What this malware does

Infostealer exfiltrating cookies, history and passwords from the Google Chrome browser, as well as attempting to do a webcam photo. Data are sent to a Discord webhook. Malicious code is split over multiple files.

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

Campaign: 2024-08-old-threading-assistant

Reasons (based on the campaign):

infostealer
typosquatting

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

94c681cc1f469c5e74cf129c4a7cc37602b47bcad02857e98d278b8a1f5f25c6

b7b431362a8fc3af245e62278011eb007f0b23eeaa959c3a34bbb959fa549a4c

41ce19661f27267642c2cd2098c7e7d5f0bdb39bae5ddbf60f97482f78e40e6e

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

Campaign

2024-08-old-threading-assistant

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks threading-assistant-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