Which versions of bunrlef are malicious?

The following RubyGems versions of bunrlef are flagged malicious: 1.0.47893. Treat any of these as compromised.

How do I remediate bunrlef if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunrlef (version 1.0.47893).

Malicious package

bunrlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunrlef (RubyGems)

MAL-2026-17117

Immediate action

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

gem uninstall bunrlef

Malicious versions

1 flagged

1.0.47893

Indicators of compromise (SHA-256)

320ea45c3820355663cbb2c416e75e05760058234e3f941045dead5b77baf63e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07803

Credits

ReversingLabs · finder

Detect & block this

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