Which versions of github-kredz are malicious?

The following RubyGems versions of github-kredz are flagged malicious: 1.0.1.1135.gf4a4623f5. Treat any of these as compromised.

How do I remediate github-kredz if I installed it?

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

If github-kredz 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 github-kredz across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for github-kredz (version 1.0.1.1135.gf4a4623f5).

Malicious package

github-kredzRubyGems

github-kredz is a confirmed malicious RubyGems package (MAL-2025-46908) that executes malicious code on install (malicious version 1.0.1.1135.gf4a4623f5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in github-kredz (RubyGems)

MAL-2025-46908

Immediate action

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

gem uninstall github-kredz

What this malware does

The OpenSSF Package Analysis project identified 'github-kredz' @ 1.0.1.1135.gf4a4623f5 (rubygems) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.1.1135.gf4a4623f5

Indicators of compromise (SHA-256)

537bf1dc9a46b4e69b596275e61de6d1b75ca3eeb2979bde507688f07458c088

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for github-kredz (version 1.0.1.1135.gf4a4623f5).
If you installed it — respond
Remove github-kredz 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 github-kredz 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. github-kredz on RubyGems has been identified as a malicious package (version 1.0.1.1135.gf4a4623f5 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 github-kredz-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