Which versions of lbyvpipwpi are malicious?

The following RubyGems versions of lbyvpipwpi are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate lbyvpipwpi if I installed it?

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

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

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

Search your lockfiles and build artifacts for lbyvpipwpi (version 0.0.1).

Malicious package

lbyvpipwpiRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lbyvpipwpi is a confirmed malicious RubyGems package (MAL-2026-7964) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lbyvpipwpi (RubyGems)

MAL-2026-7964

Immediate action

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

gem uninstall lbyvpipwpi

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

50c6b09bfef067fee74089d2efb5a6c8cb33f0a2524ed1d4193b51019c86544c

ace1034ce511971ef539592684532dcd226102b2e4742e3f03e9fce07736c2c4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02615RLUA-2026-08432

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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