Which versions of bundlea are malicious?

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

How do I remediate bundlea if I installed it?

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

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

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

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

Malicious package

bundleaRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlea (RubyGems)

MAL-2026-16930

Immediate action

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

gem uninstall bundlea

Malicious versions

2 flagged

1.0.01.0.12846

Indicators of compromise (SHA-256)

4a0ca547df63a2184f2fa0dc89353d5ce6635ec74045d1403639eaab3681d6c2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07616

Credits

ReversingLabs · finder

Detect & block this

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