Which versions of has-logs are malicious?

The following RubyGems versions of has-logs are flagged malicious: 0.7.0. Treat any of these as compromised.

How do I remediate has-logs if I installed it?

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

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

Yes — has-logs is associated with the RLMA-2024-05747, RLUA-2024-10266, RLUA-2026-08179 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 has-logs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for has-logs (version 0.7.0).

Malicious package

has-logsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in has-logs (RubyGems)

MAL-2024-6941

Immediate action

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

gem uninstall has-logs

Malicious versions

1 flagged

0.7.0

Indicators of compromise (SHA-256)

3f24b15da584f18ff84f359fb878ba2c4e614cc1ddd8cc6927a57162733080e3

a7b8fb3f0d5e8ea94dcab7fbde58fe48a3dd79af16ad969129059164ecc17540

f90c09938f58c353e4e29d346771660f7d2e24ac8b6e59bf96bcdfed4dca3cf1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05747RLUA-2024-10266RLUA-2026-08179

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks has-logs-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