Which versions of gemxpush21778549590 are malicious?

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

How do I remediate gemxpush21778549590 if I installed it?

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

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

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

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

Malicious package

gemxpush21778549590RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7710

Immediate action

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

gem uninstall gemxpush21778549590

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

98fad0f678f6ab794e22d633c7359ec2100b48a8fbaf5150667271ccb671b1dc

8f4cf6d17d81204e8bf8ebbb694a467fb516f43a810c4949e8e10f21dbd485c2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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