Which versions of logs-tf are malicious?

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

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

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

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

Yes — logs-tf is associated with the RLMA-2024-05783, RLUA-2024-10303, RLUA-2026-08513 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-tf across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for logs-tf (version 0.0.4).

Malicious package

logs-tfRubyGems

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

Malicious code in logs-tf (RubyGems)

MAL-2024-6977

Immediate action

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

gem uninstall logs-tf

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

2e44b7552148c5c730ed00b5cc8260eb74121c5cc0202a4a7a56b2cef594a2e8

4c671fff85f2534c944294b3d9b8984f49bbc671d26c2b3a649bd0b6734d9a3b

cc7ec221242d9af4d71580d52e3d0af4084ee0a9c2769282a8112ad3805947ab

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05783RLUA-2024-10303RLUA-2026-08513

References

Credits

ReversingLabs · finder

Detect & block this

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