Which versions of http-statsd are malicious?

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

How do I remediate http-statsd if I installed it?

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

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

Yes — http-statsd is associated with the RLMA-2024-05751, RLUA-2024-10270, RLUA-2026-08221 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 http-statsd across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for http-statsd (version 0.0.2).

Malicious package

http-statsdRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

http-statsd is a confirmed malicious RubyGems package (MAL-2024-6945) 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 http-statsd (RubyGems)

MAL-2024-6945

Immediate action

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

gem uninstall http-statsd

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

3ccae9a6e9bb9b3a4379ff86e3c364e03854a47ed88b4a130b96dd6c591499fa

1a6f071bf6932f9c8343dea55750f28b2fdfb7640a008f299423f9af1163c05e

0443ff5344f58fce653f41292da0af4b60427305954af69d902bd370720401bd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for http-statsd (version 0.0.2).
If you installed it — respond
Remove http-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 http-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. http-statsd 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-05751RLUA-2024-10270RLUA-2026-08221

References

Credits

ReversingLabs · finder

Detect & block this

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