Which versions of bunduer are malicious?

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

How do I remediate bunduer if I installed it?

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

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

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

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

Malicious package

bunduerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunduer (RubyGems)

MAL-2026-17020

Immediate action

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

gem uninstall bunduer

Malicious versions

2 flagged

1.0.01.0.86833

Indicators of compromise (SHA-256)

1353820380059fb8390c9092ba813b12a968c916d923848c65429ac329a58f33

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07706

Credits

ReversingLabs · finder

Detect & block this

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