Which versions of assistant-threader are malicious?

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

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

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

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

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

Malicious package

assistant-threaderPyPI

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

MAL-2024-12208

Immediate action

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

pip uninstall assistant-threader

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)

a1ea430d621b41fba4e0735ae902c78d200821e06ff696c3907b2b632b95b158

6dba125172b57e6b24bcd2cc0df076483e1fe36d1969f37e533d611fb6f9d808

19f7a11b85b828890424a45fcd7edfa7d4cc2109747eaab372bb5c191b35db4e

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 assistant-threader (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging assistant-threader across your stack and pipelines.
If you installed it — respond
assistant-threader 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 assistant-threader 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 assistant-threader 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. assistant-threader 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 assistant-threader-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