Which versions of bundlef-rb are malicious?

The following RubyGems versions of bundlef-rb are flagged malicious: 1.0.37113. Treat any of these as compromised.

How do I remediate bundlef-rb if I installed it?

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

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

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

Search your lockfiles and build artifacts for bundlef-rb (version 1.0.37113).

Malicious package

bundlef-rbRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlef-rb (RubyGems)

MAL-2026-16941

Immediate action

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

gem uninstall bundlef-rb

Malicious versions

1 flagged

1.0.37113

Indicators of compromise (SHA-256)

fd13e00ddf1a3de50e843a6c5e32df1a99949c3a3bff60ce286d1e8f0babb92b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07627

Credits

ReversingLabs · finder

Detect & block this

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