Which versions of bunlef are malicious?

The following RubyGems versions of bunlef are flagged malicious: 1.0.55825. Treat any of these as compromised.

How do I remediate bunlef if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunlef (version 1.0.55825).

Malicious package

bunlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunlef (RubyGems)

MAL-2026-17088

Immediate action

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

gem uninstall bunlef

Malicious versions

1 flagged

1.0.55825

Indicators of compromise (SHA-256)

aa17dfdb7e7d0f48b9c7812f5336105e9df7c0532a49cf72f2eeca3ac2b84be5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07774

Credits

ReversingLabs · finder

Detect & block this

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