Which versions of bunclef are malicious?

The following RubyGems versions of bunclef are flagged malicious: 1.0.0, 1.0.55168. Treat any of these as compromised.

How do I remediate bunclef if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunclef (2 malicious versions).

Malicious package

bunclefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bunclef is a confirmed malicious RubyGems package (MAL-2026-16902) that executes malicious code on install (malicious versions 1.0.0, 1.0.55168). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bunclef (RubyGems)

MAL-2026-16902

Immediate action

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

gem uninstall bunclef

Malicious versions

2 flagged

1.0.01.0.55168

Indicators of compromise (SHA-256)

21016ebad3a514f6d376358354ef14fe866dbead07a591c34525ab4e29f315ed

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07588

Credits

ReversingLabs · finder

Detect & block this

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