Which versions of lbifxeuorg are malicious?

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

How do I remediate lbifxeuorg if I installed it?

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

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

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

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

Malicious package

lbifxeuorgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7925

Immediate action

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

gem uninstall lbifxeuorg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1f7cab900727ba418742ad59c468832bbc073642729bdb067f0244b6eaa91f6f

221b52cccbf7cae65917cc1907fcbdc53b7d833c79f86fd617523c4380ff7d8e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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