Which versions of ebay-trading are malicious?

The following RubyGems versions of ebay-trading are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate ebay-trading if I installed it?

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

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

Yes — ebay-trading is associated with the RLMA-2024-05687, RLUA-2024-10206, RLUA-2026-08030 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-trading across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ebay-trading (version 0.0.2).

Malicious package

ebay-tradingRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in ebay-trading (RubyGems)

MAL-2024-6881

Immediate action

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

gem uninstall ebay-trading

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

3c17192836410db915a1515d9ef739147753f000452fea90ab8f29d31cc939be

39d8d0aec14439e5bda6180166e2f160436f8baa5f21b83768b7e2ce9f71ca00

485b0eb72e779e549ba6adc91bc5c3b2fb5e69c2e50c481f7fae32b95a5e974e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05687RLUA-2024-10206RLUA-2026-08030

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ebay-trading-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