Which versions of bunolef are malicious?

The following RubyGems versions of bunolef are flagged malicious: 1.0.41872. Treat any of these as compromised.

How do I remediate bunolef if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunolef (version 1.0.41872).

Malicious package

bunolefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunolef (RubyGems)

MAL-2026-17111

Immediate action

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

gem uninstall bunolef

Malicious versions

1 flagged

1.0.41872

Indicators of compromise (SHA-256)

77ce112d8eb54b97dffce893c630362d4797b1c53ee1eb9b5f7aec33172a98dc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07797

Credits

ReversingLabs · finder

Detect & block this

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