Which versions of bundelf are malicious?

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

How do I remediate bundelf if I installed it?

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

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

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

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

Malicious package

bundelfRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundelf (RubyGems)

MAL-2026-16915

Immediate action

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

gem uninstall bundelf

Malicious versions

2 flagged

1.0.01.0.17362

Indicators of compromise (SHA-256)

1660be30407ae75d48a8fd46f4ab1ddc7d1c791c7083ea3e506fc888ddce21d0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07601

Credits

ReversingLabs · finder

Detect & block this

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