Which versions of omniauth_mixer are malicious?

The following RubyGems versions of omniauth_mixer are flagged malicious: 0.1.2. Treat any of these as compromised.

How do I remediate omniauth_mixer if I installed it?

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

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

Yes — omniauth_mixer is associated with the RLMA-2024-05807, RLUA-2024-10328, RLUA-2026-08930 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_mixer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for omniauth_mixer (version 0.1.2).

Malicious package

omniauth_mixerRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in omniauth_mixer (RubyGems)

MAL-2024-7001

Immediate action

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

gem uninstall omniauth_mixer

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

e161953ecff18259a609f1b94df3372c93946bdddf7b3320d07cf4bdc676ecf9

02ae62554d33fbcba3be5275f6124c72b0c675dfd7f75a5f28238bb41a0d324f

ecea8d29f08c542566cd9645d4ac9685ef0f79d033214f1eda1b6d759d8848b8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05807RLUA-2024-10328RLUA-2026-08930

References

Credits

ReversingLabs · finder

Detect & block this

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