Which versions of lbjjpuyqqs are malicious?

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

How do I remediate lbjjpuyqqs if I installed it?

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

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

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

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

Malicious package

lbjjpuyqqsRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7926

Immediate action

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

gem uninstall lbjjpuyqqs

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6aee6c91137a72a6a9caab07a9ee31874ad267c622326a55da15ed18338a164f

5d5b4e6a7410dac6af63e815b3c31c3bf8f5645e5465dbda166bc4a8cf38f1fb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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