Which versions of l0pxstat are malicious?

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

How do I remediate l0pxstat if I installed it?

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

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

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

Search your lockfiles and build artifacts for l0pxstat (2 malicious versions).

Malicious package

l0pxstatRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

l0pxstat is a confirmed malicious RubyGems package (MAL-2026-7781) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in l0pxstat (RubyGems)

MAL-2026-7781

Immediate action

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

gem uninstall l0pxstat

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

9edd92cfee8eeed621d8978f742130a9e27cd9e4ee5c17e8c1ef348ca2758892

090d000ac6d9dadd77fd5bc818615b2434c6092c4a876c629fb0c00b3ef0af98

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02432RLUA-2026-08247

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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