Which versions of hlokty are malicious?

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

How do I remediate hlokty if I installed it?

Remove hlokty from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed hlokty — how do I know if it already compromised me?

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

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

Malicious package

hloktyPyPI

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

MAL-2024-5203

Immediate action

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

pip uninstall hlokty

What this malware does

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: 2023-12-kitty

Reasons (based on the campaign):

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

ae263a2bbebe79c606fcbcea0c6305d8ea45ea093dd2616eb5d076278f9ea248

4c14d595a65722d6842c2e3fc653f85d6b423e92bd160e5550601fa52697051e

9d38850b31f1007b381b7d9350b3369d42d18b668b2168576a4dfa14c4e4b90a

5a87204da4f0d5ef08a7731badb5036e3551f20695a5491b1f07b617c568c8af

8492b563e3c47210f06f5235de064ff54c84f9cb67ea790d140f74a4eeedd54a

a07f435bd12046b331e7eafe8dd61ce13488f930e594ebb45b2b672d09470745

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hlokty (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hlokty across your stack and pipelines.
If you installed it — respond
Remove hlokty from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If hlokty 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 hlokty 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. hlokty 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-2024-03985RLUA-2024-083462023-12-kittyRLUA-2026-00393

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks hlokty-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring