Which versions of bundlaf are malicious?

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

How do I remediate bundlaf if I installed it?

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

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

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

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

Malicious package

bundlafRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlaf (RubyGems)

MAL-2026-16926

Immediate action

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

gem uninstall bundlaf

Malicious versions

2 flagged

1.0.01.0.66618

Indicators of compromise (SHA-256)

34bba33cb0383fd795d9aa2fa49151086c37f9a8469dd4759b77ad9aa5c8a4be

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07612

Credits

ReversingLabs · finder

Detect & block this

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