Which versions of bunoler are malicious?

The following RubyGems versions of bunoler are flagged malicious: 1.0.68082. Treat any of these as compromised.

How do I remediate bunoler if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunoler (version 1.0.68082).

Malicious package

bunolerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunoler (RubyGems)

MAL-2026-17112

Immediate action

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

gem uninstall bunoler

Malicious versions

1 flagged

1.0.68082

Indicators of compromise (SHA-256)

c8b0b3a96ca7e58489c04b95b6bc4216704a74aa696838f561d35705aeac8caa

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07798

Credits

ReversingLabs · finder

Detect & block this

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