Which versions of bundlef are malicious?

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

How do I remediate bundlef if I installed it?

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

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

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

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

Malicious package

bundlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlef (RubyGems)

MAL-2026-16938

Immediate action

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

gem uninstall bundlef

Malicious versions

2 flagged

1.0.01.0.58293

Indicators of compromise (SHA-256)

c14906bc0891baa21840baa2087869a3e38c8ea03e00893b47d2276bbb6bcce1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07624

Credits

ReversingLabs · finder

Detect & block this

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