Which versions of ebay_ysr are malicious?

The following RubyGems versions of ebay_ysr are flagged malicious: 0.1.8. Treat any of these as compromised.

How do I remediate ebay_ysr if I installed it?

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

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

Yes — ebay_ysr is associated with the RLMA-2024-05688, RLUA-2024-10207, RLUA-2026-08031 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 ebay_ysr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ebay_ysr (version 0.1.8).

Malicious package

ebay_ysrRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

ebay_ysr is a confirmed malicious RubyGems package (MAL-2024-6882) that executes malicious code on install (malicious version 0.1.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ebay_ysr (RubyGems)

MAL-2024-6882

Immediate action

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

gem uninstall ebay_ysr

Malicious versions

1 flagged

0.1.8

Indicators of compromise (SHA-256)

f2fded8a87b6f6b32f7f689fd0ce76bf259fc41c272a9346cb876f08d85031ff

d6ce467b9873774f55cb9a632155db8c33c23a9589f2aecb661585a01f13652d

c071c83ba060ebcb23b848114ff1a7528d5848d5fec9ab30dcdbccfeb97e8839

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ebay_ysr (version 0.1.8).
If you installed it — respond
Remove ebay_ysr 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 ebay_ysr 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. ebay_ysr on RubyGems has been identified as a malicious package (version 0.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05688RLUA-2024-10207RLUA-2026-08031

References

Credits

ReversingLabs · finder

Detect & block this

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