Which versions of prometheus_client_ruby are malicious?

The following RubyGems versions of prometheus_client_ruby are flagged malicious: 0.0.900, 0.1.900, 0.900.0, 1.900, 9002.0. Treat any of these as compromised.

How do I remediate prometheus_client_ruby if I installed it?

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

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

Yes — prometheus_client_ruby is associated with the RLMA-2025-06622, RLUA-2026-08953 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 prometheus_client_ruby across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for prometheus_client_ruby (5 malicious versions).

Malicious package

prometheus_client_rubyRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

prometheus_client_ruby is a confirmed malicious RubyGems package (MAL-2025-192912) that executes malicious code on install (malicious versions 0.0.900, 0.1.900, 0.900.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in prometheus_client_ruby (RubyGems)

MAL-2025-192912

Immediate action

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

gem uninstall prometheus_client_ruby

Malicious versions

5 flagged

0.0.9000.1.9000.900.01.9009002.0

Indicators of compromise (SHA-256)

eb97a2530840934448d11a9d586f85241277886646efffbdfe320c40e315f676

644364f533688bd0d0ab61e51808c836ed2d69825b5b8b94402c623ee03ad8f8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06622RLUA-2026-08953

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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