Which versions of bundlaef are malicious?

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

How do I remediate bundlaef if I installed it?

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

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

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

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

Malicious package

bundlaefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlaef (RubyGems)

MAL-2026-16924

Immediate action

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

gem uninstall bundlaef

Malicious versions

2 flagged

1.0.01.0.44794

Indicators of compromise (SHA-256)

ea315fce65ad2806a9ca27fd6f33a0211616a572062f122ec112fe6c9ae2b3b4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07610

Credits

ReversingLabs · finder

Detect & block this

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