Which versions of lbyliylvym are malicious?

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

How do I remediate lbyliylvym if I installed it?

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

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

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

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

Malicious package

lbyliylvymRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7963

Immediate action

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

gem uninstall lbyliylvym

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cdd5cb35012d517fdd204d59b71baa789351c31b03dcf3fbd352fa0a58c1f0fd

a78f6a2bffdd81ca7dc0d3c4e8694953029064a7064c4a2093b34c10eb5be604

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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