Which versions of kekiktaban are malicious?

The following PyPI versions of kekiktaban are flagged malicious: 0.5.0, 0.6.0. Treat any of these as compromised.

How do I remediate kekiktaban if I installed it?

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

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

Yes — kekiktaban is associated with the RLMA-2024-11074, 2024-10-kekiktaban, RLUA-2026-00450 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 kekiktaban 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 kekiktaban (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kekiktaban across your stack and pipelines.

Malicious package

kekiktabanPyPI

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

MAL-2024-11620

Immediate action

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

pip uninstall kekiktaban

What this malware does

Obfuscated package containing multiple techniques detecting sandboxing and exfiltrating basic data to a telegram webhook, with a little other functionality

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

Campaign: 2024-10-kekiktaban

Reasons (based on the campaign):

obfuscation
A Telegram webhook is used to send collected data.
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

2 flagged

0.5.00.6.0

Indicators of compromise (SHA-256)

a37bcce0d9ab3462cb9c6a28502e3bb93a8d962c025f61354cb6caf714e5404e

1f376baeef8d4c70a3037abe44232c5e21add2b2b81ada605a3f93cb7774dfc7

80c5f1e8e195c782d87e63c2bfc7eac3febe17836c3d502594ea10524f97464e

e7cf8f4c9db7b6a01e4a65f98098f446ba407745192919c788ce5f0e38fd37a9

e1457355e77eb976c19f65b03947dc428ffac01ff49042f3baa6f8e0af007ec8

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

Campaign

RLMA-2024-110742024-10-kekiktabanRLUA-2026-00450

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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