Which versions of bunulef are malicious?

The following RubyGems versions of bunulef are flagged malicious: 1.0.44288. Treat any of these as compromised.

How do I remediate bunulef if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunulef (version 1.0.44288).

Malicious package

bunulefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunulef (RubyGems)

MAL-2026-17126

Immediate action

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

gem uninstall bunulef

Malicious versions

1 flagged

1.0.44288

Indicators of compromise (SHA-256)

4f034119cae36a4e3e806f5408560eb4d67552b6056e112b547f280a802898a6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07815

Credits

ReversingLabs · finder

Detect & block this

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