Which versions of lbrssftspjbqe are malicious?

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

How do I remediate lbrssftspjbqe if I installed it?

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

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

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

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

Malicious package

lbrssftspjbqeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7946

Immediate action

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

gem uninstall lbrssftspjbqe

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f034e7a9de6418b2ff181edca1d1d32c745de25eb0b9d4cb03c31026cba5db2f

0df76dac17f35427ee47b1c4a48ebd251d2c454b5d879fd74f48da7bf84684c4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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