Which versions of lev174518561 are malicious?

The following RubyGems versions of lev174518561 are flagged malicious: 0.0.68561. Treat any of these as compromised.

How do I remediate lev174518561 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lev174518561 (version 0.0.68561).

Malicious package

lev174518561RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lev174518561 (RubyGems)

MAL-2026-7991

Immediate action

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

gem uninstall lev174518561

Malicious versions

1 flagged

0.0.68561

Indicators of compromise (SHA-256)

3b890b92c18df3b3fe1828db467017f6e01c8faf9be9a58258e2a1534affe926

8fe936de73da65cd52c60fdbb8ff92f429d35e3d4777f24d25c8dc7439a9db3a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02642RLUA-2026-08459

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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