Which versions of bundeer are malicious?

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

How do I remediate bundeer if I installed it?

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

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

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

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

Malicious package

bundeerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundeer (RubyGems)

MAL-2026-16911

Immediate action

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

gem uninstall bundeer

Malicious versions

2 flagged

1.0.01.0.17600

Indicators of compromise (SHA-256)

dbaad8af814df9287b0b6b1f6ec0efa20bdc21fae949662b10fb9997fd9de557

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07597

Credits

ReversingLabs · finder

Detect & block this

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