Which versions of btcflx are malicious?

The following PyPI versions of btcflx are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate btcflx if I installed it?

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

If btcflx was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is btcflx part of a known attack campaign?

Yes — btcflx is associated with the 2026-08-kotanku, IN-MAL-2026-017208 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 btcflx across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for btcflx (version 0.1.0).

Malicious package

btcflxPyPI

Advisory published Aug 10, 2026Updated Aug 10, 2026

btcflx is a confirmed malicious PyPI package (MAL-2026-13682) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in btcflx (PyPI)

MAL-2026-13682

Immediate action

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

pip uninstall btcflx

What this malware does

Package advertises itself as an HTTP speed-up library but on import of the top-level module unconditionally locates the user's Monero wallet directory (Windows C:\Users<user>\Documents\Monero, Linux /home/<user>/Monero), kills running 'feather' and 'monero' processes to release file locks, archives the directory, and uploads it via api.telegram.org sendDocument to a hardcoded Telegram bot with chat_id -5044692933. A companion sendMessage call reports host reconnaissance status ('Found wallet... sending' / 'Did not find wallets') to the same chat. The Telegram bot token and both Monero directory paths are base64-encoded in source to hide the destination and targets. Package name and description do not mention cryptocurrency wallets, establishing a cover-story mismatch.

During import, the package exfiltrates cryptocurrency wallet files.

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

Campaign: 2026-08-kotanku

Reasons (based on the campaign):

exfiltration-crypto
uses-telegram-bot

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

504aca220be0f03b6572f62dc3fc4a49ace09be61a969e39713c890f28afe62a

839c411e8d33badaebd5e59b2d966dc000e631843a49ce9352caafd1b7dd9e12

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for btcflx (version 0.1.0).
If you installed it — respond
btcflx 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 btcflx was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. btcflx on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-08-kotankuIN-MAL-2026-017208

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database