Which versions of crl-watchdog are malicious?

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

How do I remediate crl-watchdog if I installed it?

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

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

Yes — crl-watchdog is associated with the RLMA-2024-05650, RLUA-2024-10169, RLUA-2026-07947 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 crl-watchdog across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for crl-watchdog (version 1.0.0).

Malicious package

crl-watchdogRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

crl-watchdog is a confirmed malicious RubyGems package (MAL-2024-6844) 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 crl-watchdog (RubyGems)

MAL-2024-6844

Immediate action

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

gem uninstall crl-watchdog

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f38c56067e9c9d41d78258fb92def29aa168a26e604a21d84a061da306f74893

43784aaeab4c44706d2f37225cb0b7aefd5cc0e6a73a88c8f1f4aaff316c8502

a9e7ff945da6b478c93a8b29e75bc88ed6ff612fc3578356b5ddc90af08ae3a1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for crl-watchdog (version 1.0.0).
If you installed it — respond
Remove crl-watchdog 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 crl-watchdog 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. crl-watchdog 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-05650RLUA-2024-10169RLUA-2026-07947

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks crl-watchdog-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