Which versions of bundaef are malicious?

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

How do I remediate bundaef if I installed it?

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

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

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

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

Malicious package

bundaefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundaef (RubyGems)

MAL-2026-16904

Immediate action

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

gem uninstall bundaef

Malicious versions

2 flagged

1.0.01.0.64189

Indicators of compromise (SHA-256)

904c51ddc0f6d8969dcda2f8e59a0ea494f624224cf0ca2f1bd07dbe6b4e81d6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07590

Credits

ReversingLabs · finder

Detect & block this

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