What does the kerokwis malware do?

The OpenSSF Package Analysis project identified 'kerokwis' @ 99 (rubygems) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of kerokwis are malicious?

The following RubyGems versions of kerokwis are flagged malicious: 99. Treat any of these as compromised.

How do I remediate kerokwis if I installed it?

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

If kerokwis was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find kerokwis across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kerokwis (version 99).

Malicious package

kerokwisRubyGems

Advisory published Sep 22, 2026Updated Sep 22, 2026

kerokwis is a confirmed malicious RubyGems package (MAL-2026-16420) that executes malicious code on install (malicious version 99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kerokwis (RubyGems)

MAL-2026-16420

Immediate action

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

gem uninstall kerokwis

What this malware does

The OpenSSF Package Analysis project identified 'kerokwis' @ 99 (rubygems) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

b2921b86b5414d75ef09db29e36e70d66085361090c4a55f83878b14463996ef

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for kerokwis (version 99).
If you installed it — respond
Remove kerokwis 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 kerokwis was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. kerokwis on RubyGems has been identified as a malicious package (version 99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database