Which versions of biundper are malicious?

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

How do I remediate biundper if I installed it?

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

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

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

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

Malicious package

biundperRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundper (RubyGems)

MAL-2026-16687

Immediate action

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

gem uninstall biundper

Malicious versions

2 flagged

1.0.01.0.32876

Indicators of compromise (SHA-256)

22216f67e9b086944035f461f6b0b7366c5ddc9a7d400dc0cc89abd9a85e561f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07351

Credits

ReversingLabs · finder

Detect & block this

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