Which versions of bundlefl are malicious?

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

How do I remediate bundlefl if I installed it?

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

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

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

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

Malicious package

bundleflRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlefl (RubyGems)

MAL-2026-16947

Immediate action

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

gem uninstall bundlefl

Malicious versions

2 flagged

1.0.01.0.14431

Indicators of compromise (SHA-256)

46f7e6d2edcc529330dbf3eb6305603f9d6b22b580def9bb5a9bf1f18367cd92

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07633

Credits

ReversingLabs · finder

Detect & block this

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