Which versions of bunfler are malicious?

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

How do I remediate bunfler if I installed it?

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

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

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

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

Malicious package

bunflerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunfler (RubyGems)

MAL-2026-17028

Immediate action

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

gem uninstall bunfler

Malicious versions

2 flagged

1.0.01.0.59795

Indicators of compromise (SHA-256)

131853f02ced62c7eae35dd23d7c232f6aea579733dddcf5762d1f814a8019c6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07714

Credits

ReversingLabs · finder

Detect & block this

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