Which versions of jenkins-statsd are malicious?

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

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

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

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

Yes — jenkins-statsd is associated with the RLMA-2024-05756, RLUA-2024-10275, RLUA-2026-08239 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 jenkins-statsd across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jenkins-statsd (version 0.3.1).

Malicious package

jenkins-statsdRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in jenkins-statsd (RubyGems)

MAL-2024-6950

Immediate action

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

gem uninstall jenkins-statsd

Malicious versions

1 flagged

0.3.1

Indicators of compromise (SHA-256)

9f7f1f0094c162f485686c90f6e63ac5091ae88f382822fa70b89cd3f2b8ce43

fd1017e405839af628a46b64ffe153c425f802e58c683ea6051bd267c8f0f42c

829a15f25649ce25d793354ffc4e951da0916b73cd70eff8f8773112cbb40a10

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05756RLUA-2024-10275RLUA-2026-08239

References

Credits

ReversingLabs · finder

Detect & block this

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