Which versions of gemx559383abc are malicious?

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

How do I remediate gemx559383abc if I installed it?

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

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

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

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

Malicious package

gemx559383abcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7709

Immediate action

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

gem uninstall gemx559383abc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9de5bdb60516d6577496536907f8bc1c2f01056f84dde91fb1ec807ddf5aaeb6

10978bbf27fadb709482d23f855f401b71adf2c1c17573c51c52ea37e00c00e7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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