Which versions of ylam31778568568 are malicious?

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

How do I remediate ylam31778568568 if I installed it?

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

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

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

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

Malicious package

ylam31778568568RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9558

Immediate action

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

gem uninstall ylam31778568568

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9f68f5da4c9328dcbd394ab0b51c60cfe71c4d1659ab400c0301a20b1bf9cdd2

ca2b9d4bb36819ee9118238c52cf825b06c8c2ab6a86226c86a9468e5358862e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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