Which versions of bundoef are malicious?

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

How do I remediate bundoef if I installed it?

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

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

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

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

Malicious package

bundoefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundoef (RubyGems)

MAL-2026-17009

Immediate action

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

gem uninstall bundoef

Malicious versions

2 flagged

1.0.01.0.69592

Indicators of compromise (SHA-256)

00347477118493e5862f4edf2c419a21a9d8cb707b721b699be020c6e56e682a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07695

Credits

ReversingLabs · finder

Detect & block this

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