Which versions of yardxabc888 are malicious?

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

How do I remediate yardxabc888 if I installed it?

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

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

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

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

Malicious package

yardxabc888RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9553

Immediate action

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

gem uninstall yardxabc888

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b37b382cc838baaae0624c6afbffea899c07a04812475e941371814f61e9310e

17e580d2153ac3f9a0814739346aa1b40387a70c565a7b226601eed1e9ad0ef6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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