Which versions of biundlesr are malicious?

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

How do I remediate biundlesr if I installed it?

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

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

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

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

Malicious package

biundlesrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlesr (RubyGems)

MAL-2026-16667

Immediate action

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

gem uninstall biundlesr

Malicious versions

2 flagged

1.0.01.0.72337

Indicators of compromise (SHA-256)

6efb65d4ef235843311d12275be64e3629e4a053faf1b5bd01c5fd2dab384ed5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07331

Credits

ReversingLabs · finder

Detect & block this

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