Which versions of bundlera are malicious?

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

How do I remediate bundlera if I installed it?

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

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

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

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

Malicious package

bundleraRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlera (RubyGems)

MAL-2026-16966

Immediate action

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

gem uninstall bundlera

Malicious versions

2 flagged

1.0.01.0.55692

Indicators of compromise (SHA-256)

76815f41fa72f2df90ceadc586f3dc64607947c3cf8a20b88ec3af8e3b07d49a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07652

Credits

ReversingLabs · finder

Detect & block this

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