Which versions of akh-py are malicious?

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

How do I remediate akh-py if I installed it?

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

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

Yes — akh-py is associated with the RLMA-2024-10963, GENERIC-standard-pypi-install-pentest, RLUA-2026-00052 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 akh-py 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 akh-py (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 akh-py across your stack and pipelines.

Malicious package

akh-pyPyPI

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

MAL-2024-11520

Immediate action

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

pip uninstall akh-py

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

24785009f9ad0498777003d617f9a8100b43fa13218b8a3edb0cd9ad241d3a4c

90048da51ba492cb73a605467deeb410def2b75dc8aa0edaefc8d53efedaa696

9e1af18204b91fa245349f10eea1049681afa1d91cb4dd21a81b7789a29a9333

ea57d07153b70e2c422ee0f35dabb9dee8cc1d46b73dff6001b52d4073fe1ecd

d060ab57bbbdc922db9b78ede0afaeff68b8b58a910efe845cd33f18cea1ffd9

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 akh-py (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 akh-py across your stack and pipelines.
If you installed it — respond
akh-py 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 akh-py 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 akh-py 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. akh-py 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-10963GENERIC-standard-pypi-install-pentestRLUA-2026-00052

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks akh-py-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