Which versions of bundlsr are malicious?

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

How do I remediate bundlsr if I installed it?

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

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

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

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

Malicious package

bundlsrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlsr (RubyGems)

MAL-2026-17002

Immediate action

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

gem uninstall bundlsr

Malicious versions

2 flagged

1.0.01.0.73267

Indicators of compromise (SHA-256)

0b8cef442ca1e64820d1c8b521b37534d2a09249bea46025fba2757a8de3bd30

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07688

Credits

ReversingLabs · finder

Detect & block this

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