Which versions of biundlsr are malicious?

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

How do I remediate biundlsr if I installed it?

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

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

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

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

Malicious package

biundlsrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlsr (RubyGems)

MAL-2026-16681

Immediate action

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

gem uninstall biundlsr

Malicious versions

2 flagged

1.0.01.0.25965

Indicators of compromise (SHA-256)

9af3e399cf4e33c4321e3fb2b8c25cc1daf7847b7e0c6a4ca1c0a1020f44b1a5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07345

Credits

ReversingLabs · finder

Detect & block this

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