Which versions of lbtyldorgi are malicious?

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

How do I remediate lbtyldorgi if I installed it?

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

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

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

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

Malicious package

lbtyldorgiRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7961

Immediate action

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

gem uninstall lbtyldorgi

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

872cc4ce74fc5cae3147ea98f54a7e6752d9a8d6ecf6834b4585c17890de962d

d415f17e2c43f8d03e5b2c92cff1e35716b2a151409db9e342f99708e036aa6f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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