Which versions of bundkef are malicious?

The following RubyGems versions of bundkef are flagged malicious: 1.0.0, 1.0.40256. Treat any of these as compromised.

How do I remediate bundkef if I installed it?

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

If bundkef 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.

Is bundkef part of a known attack campaign?

Yes — bundkef is associated with the RLMA-2026-07608 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 bundkef across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bundkef (2 malicious versions).

Malicious package

bundkefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bundkef is a confirmed malicious RubyGems package (MAL-2026-16922) that executes malicious code on install (malicious versions 1.0.0, 1.0.40256). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundkef (RubyGems)

MAL-2026-16922

Immediate action

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

gem uninstall bundkef

Malicious versions

2 flagged

1.0.01.0.40256

Indicators of compromise (SHA-256)

af52f7db5f22f05409fd5fb2894c2cf765670866772c30a8e1a8ef16cafb93e4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bundkef (2 malicious versions).
If you installed it — respond
Remove bundkef 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 bundkef 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. bundkef on RubyGems has been identified as a malicious package (versions 1.0.0, 1.0.40256 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-07608

Credits

ReversingLabs · finder

Detect & block this

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