Which versions of gemxy-1778522681 are malicious?

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

How do I remediate gemxy-1778522681 if I installed it?

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

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

Yes — gemxy-1778522681 is associated with the RLMA-2026-02362, RLUA-2026-08144 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 gemxy-1778522681 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gemxy-1778522681 (2 malicious versions).

Malicious package

gemxy-1778522681RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

gemxy-1778522681 is a confirmed malicious RubyGems package (MAL-2026-7711) 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 gemxy-1778522681 (RubyGems)

MAL-2026-7711

Immediate action

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

gem uninstall gemxy-1778522681

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

af929cc704d4aedf72ff7e6cd975477c5419b9ed5fd229e6e0f4d9000ed37a6d

18a263b165dce3aee65d376cac8b2a172e5231f86f5bea668efaee08e764810c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for gemxy-1778522681 (2 malicious versions).
If you installed it — respond
Remove gemxy-1778522681 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 gemxy-1778522681 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. gemxy-1778522681 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-02362RLUA-2026-08144

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks gemxy-1778522681-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