Which versions of kersa are malicious?

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

How do I remediate kersa if I installed it?

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

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

Yes — kersa is associated with the RLMA-2024-11075, 2024-09-bondonioanderas-cryptominer, RLUA-2026-00451 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 kersa 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 kersa (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kersa across your stack and pipelines.

Malicious package

kersaPyPI

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

MAL-2024-11621

Immediate action

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

pip uninstall kersa

What this malware does

During installation, a cryptominer is secretly installed and started.

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

Campaign: 2024-09-bondonioanderas-cryptominer

Reasons (based on the campaign):

cryptominer
The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

0b5970fc83c3c8e74b53c5ffcdd007aeb7a6ac97727427953ee2cfa5eb88b168

7a7c14c07febc40085b168373a08d740c1674bf5b99770055357df6441109b92

d622fba4f0f9e74871fb87964bdc3818e244e0f9669a814ae71b923ff699e9be

f0dcf6d4c57719a718129f72f9c8d54b2df1b13cc81ea4f67e05a5a4ead22582

5dd240552ca44523d6bfdf92c65a715c144e7c1e90029f69cb46205e454f9f09

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 kersa (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kersa across your stack and pipelines.
If you installed it — respond
kersa 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 kersa 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 kersa 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. kersa 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-110752024-09-bondonioanderas-cryptominerRLUA-2026-00451

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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