Which versions of lbrssltutuvwp are malicious?

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

How do I remediate lbrssltutuvwp if I installed it?

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

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

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

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

Malicious package

lbrssltutuvwpRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lbrssltutuvwp is a confirmed malicious RubyGems package (MAL-2026-7947) 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 lbrssltutuvwp (RubyGems)

MAL-2026-7947

Immediate action

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

gem uninstall lbrssltutuvwp

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4d5ad547912ac45132e41f31b1d9a695a2a6914ad7fdbd147c21678c24ca85b3

ff6be5dc3781ba932f11e5bbe04e365f02e24e3a1dcf2bd9be023b440ae5faf8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lbrssltutuvwp (version 0.0.1).
If you installed it — respond
Remove lbrssltutuvwp 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 lbrssltutuvwp 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. lbrssltutuvwp 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-02598RLUA-2026-08415

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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