Which versions of omniauth_ebay are malicious?

The following RubyGems versions of omniauth_ebay are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate omniauth_ebay if I installed it?

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

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

Yes — omniauth_ebay is associated with the RLMA-2024-05804, RLUA-2024-10325, RLUA-2026-08927 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 omniauth_ebay across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for omniauth_ebay (version 1.0).

Malicious package

omniauth_ebayRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in omniauth_ebay (RubyGems)

MAL-2024-6998

Immediate action

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

gem uninstall omniauth_ebay

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

3c150c5534550a0285f9403e02c753a1b20cc78b1dfa06d1201980dfdcb15685

4a6d44033dac7993a20ac07868b0184360f86d88e4f5378f8bd9a244cc60a231

bc40cc44293a258d33c0a567dcd0ab842c97f86062e19d813ad6fb1b76af4878

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05804RLUA-2024-10325RLUA-2026-08927

References

Credits

ReversingLabs · finder

Detect & block this

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