Which versions of bunoder are malicious?

The following RubyGems versions of bunoder are flagged malicious: 1.0.71936. Treat any of these as compromised.

How do I remediate bunoder if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunoder (version 1.0.71936).

Malicious package

bunoderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bunoder is a confirmed malicious RubyGems package (MAL-2026-17107) that executes malicious code on install (malicious version 1.0.71936). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bunoder (RubyGems)

MAL-2026-17107

Immediate action

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

gem uninstall bunoder

Malicious versions

1 flagged

1.0.71936

Indicators of compromise (SHA-256)

47f70be401505a9a09f83f3575985bbad1d345bbee47260d1c4c1584a34a5e39

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07793

Credits

ReversingLabs · finder

Detect & block this

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