Which versions of bundlrf are malicious?

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

How do I remediate bundlrf if I installed it?

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

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

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

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

Malicious package

bundlrfRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlrf (RubyGems)

MAL-2026-16997

Immediate action

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

gem uninstall bundlrf

Malicious versions

2 flagged

1.0.01.0.45596

Indicators of compromise (SHA-256)

2aaf75c988d956f55466dca6b24bfa560d03d2d0c6610c777360c3fb342b24f9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07683

Credits

ReversingLabs · finder

Detect & block this

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