Which versions of em_statsd are malicious?

The following RubyGems versions of em_statsd are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate em_statsd if I installed it?

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

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

Yes — em_statsd is associated with the RLMA-2024-05692, RLUA-2024-10211, RLUA-2026-08049 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 em_statsd across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for em_statsd (version 1.0.0).

Malicious package

em_statsdRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in em_statsd (RubyGems)

MAL-2024-6886

Immediate action

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

gem uninstall em_statsd

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c2c3c15600fd958d4c2db02c047737c017ef7cdf2a027e1c39685ea9c1617c90

6bb514ec4db53e250c23d39be95d7990522aaed61aa156ae8760221373f489b1

e52c76b63213db4a33615bc5399e7bc9cc7ba252d9cd9b7285b5e9ff700d3d8f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05692RLUA-2024-10211RLUA-2026-08049

References

Credits

ReversingLabs · finder

Detect & block this

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