Which versions of logs-viewer are malicious?

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

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

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

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

Yes — logs-viewer is associated with the RLMA-2024-05784, RLUA-2024-10304, RLUA-2026-08514 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 logs-viewer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for logs-viewer (version 0.2.0).

Malicious package

logs-viewerRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in logs-viewer (RubyGems)

MAL-2024-6978

Immediate action

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

gem uninstall logs-viewer

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

9eebd53c4828832b58a88dff5eae223179920a77387235fc87601af23bf5c74f

bf7f6ad6a23ce11c6e5d765a31efeffd016cc53c92ed0d8d6591481c269de43f

4c48b8dcf9d523c1afecc2fc7e3707653be85f7795c408a929b04713e1f05772

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05784RLUA-2024-10304RLUA-2026-08514

References

Credits

ReversingLabs · finder

Detect & block this

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