Which versions of bundlre are malicious?

The following RubyGems versions of bundlre are flagged malicious: 1.0.68430, 1000.0.0. Treat any of these as compromised.

How do I remediate bundlre if I installed it?

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

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

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

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

Malicious package

bundlreRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bundlre is a confirmed malicious RubyGems package (MAL-2026-16994) that executes malicious code on install (malicious versions 1.0.68430, 1000.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundlre (RubyGems)

MAL-2026-16994

Immediate action

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

gem uninstall bundlre

Malicious versions

2 flagged

1.0.684301000.0.0

Indicators of compromise (SHA-256)

edc1ae94befed5f4b1e4dcb8f0e5be8677f312d95778a226b1c9d49138950cb4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07680

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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