Which versions of emque_stats are malicious?

The following RubyGems versions of emque_stats are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate emque_stats if I installed it?

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

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

Yes — emque_stats is associated with the RLMA-2024-05695, RLUA-2024-10214, RLUA-2026-08052 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 emque_stats across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for emque_stats (version 1.1.0).

Malicious package

emque_statsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in emque_stats (RubyGems)

MAL-2024-6889

Immediate action

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

gem uninstall emque_stats

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

d3bb52fd890cb8647253057efe58872cb09e354bd79e9bb6b98fb0d5e673ac9c

bea309ddd2176a839d0bc5bdc00577a18159698f8b0f54e05a478402a33cb93d

03e5b54fee579edd2ee33517e0ee6e8f70802a805a17bbcb12d228ce59a4620b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05695RLUA-2024-10214RLUA-2026-08052

References

Credits

ReversingLabs · finder

Detect & block this

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