Which versions of threadfluent are malicious?

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

How do I remediate threadfluent if I installed it?

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

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

Yes — threadfluent is associated with the RLMA-2025-00535, 2024-12-httpfluent, RLUA-2026-00821 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 threadfluent 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 threadfluent (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging threadfluent across your stack and pipelines.

Malicious package

threadfluentPyPI

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

MAL-2025-994

Immediate action

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

pip uninstall threadfluent

What this malware does

The package contains highly obfuscated content, that install another, downloaded from a remote location obfuscated script in the installation path of the 'requests' package, and marks it as a hidden system file. In addition, another file contains a code that imitates doing some meaningful activity.

Later attempts hide the malicious code in a separated package, downloaded from Test PyPI.

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

Campaign: 2024-12-httpfluent

Reasons (based on the campaign):

obfuscation
modify-system-without-consent
Downloads and executes a remote malicious script.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

d31ac30b495b69ae18873a0614da6691165b3d9f694e22456986eb46f14c1c50

0c2925bb4bd77c07641a922cad14c876cd3bc8f46ea7683de7a1b21c2e80874b

2a72da681aea57683d0d6b134f0263f126dfe205810fdcfa970c9920058fcf15

146c6e3cdd6e7b31e1cbdb000be66fa72ea3066c7f240977f1dcc437b878a27b

dcdb231da03efea4cb2c97850d918c2b4a8788c40a3553b9b92107a3a8e563e7

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

RLMA-2025-005352024-12-httpfluentRLUA-2026-00821

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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