Which versions of lev173958552 are malicious?

The following RubyGems versions of lev173958552 are flagged malicious: 0.0.68552. Treat any of these as compromised.

How do I remediate lev173958552 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lev173958552 (version 0.0.68552).

Malicious package

lev173958552RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lev173958552 is a confirmed malicious RubyGems package (MAL-2026-7990) that executes malicious code on install (malicious version 0.0.68552). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lev173958552 (RubyGems)

MAL-2026-7990

Immediate action

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

gem uninstall lev173958552

Malicious versions

1 flagged

0.0.68552

Indicators of compromise (SHA-256)

aa4c2c81af420fdfb44ff438763f7aeecc297a9adf7fbf2fe6fea54f0b53ba71

ba86ba8bcbc7354a205ec3e152929599f98851a76cd626d3b854d371516b780e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lev173958552 (version 0.0.68552).
If you installed it — respond
Remove lev173958552 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 lev173958552 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. lev173958552 on RubyGems has been identified as a malicious package (version 0.0.68552 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02641RLUA-2026-08458

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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