Which versions of lbfajkdltu are malicious?

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

How do I remediate lbfajkdltu if I installed it?

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

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

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

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

Malicious package

lbfajkdltuRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7923

Immediate action

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

gem uninstall lbfajkdltu

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dac993dbbe3d393e455a808d65554d16747c28212dc2cfb01dc03182a3075059

da4d226ebba7686ba87b9a6103466e11cabd0294f5f68fbbd8778fb2c9b550bc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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