Which versions of pykane are malicious?

The following PyPI versions of pykane are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pykane if I installed it?

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

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

Yes — pykane is associated with the RLMA-2024-11130, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00638 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 pykane 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 pykane (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pykane across your stack and pipelines.

Malicious package

pykanePyPI

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

MAL-2024-11673

Immediate action

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

pip uninstall pykane

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d16ca1a93cca13d301a45791b2bf4489fb2b6f7d10f14e32c89c7ec5b6217a8d

7c6e99592bf4b5b871de313115ecf3ada4e3adf02771f788ad009906ab644a5a

5f0e00230ef4f47cbb9d43ffd849aa41f1e4f8b192944f56fdd49e6e24e6dc8d

3941e72166b054f6fdb57e95fd8d8e88cd644a86bd387e3186531b64c9b4fa30

3e1ba76421fd72e335f39c6bb8201bfd019c0e6063f90ef026111a813028fd17

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

Campaign

RLMA-2024-111302024-08-embeds-RealtekHDAudioManagerRLUA-2026-00638

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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