Which versions of bundaer are malicious?

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

How do I remediate bundaer if I installed it?

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

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

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

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

Malicious package

bundaerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundaer (RubyGems)

MAL-2026-16905

Immediate action

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

gem uninstall bundaer

Malicious versions

2 flagged

1.0.01.0.92631

Indicators of compromise (SHA-256)

076a569cd19b002a1eeb86319990d3dd20213f8fb589f2c74ff4e09282cba205

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07591

Credits

ReversingLabs · finder

Detect & block this

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