Which versions of ylam41778568568 are malicious?

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

How do I remediate ylam41778568568 if I installed it?

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

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

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

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

Malicious package

ylam41778568568RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9559

Immediate action

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

gem uninstall ylam41778568568

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

371b79d42a580192526650a15d73cb5e5590ee03ac349583d0b76270c6b333e2

f4c84c85b6f2ff92676254aeb2752a4b3947335054d052540a88a19a9ee91f7c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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