Which versions of cwlogs_s3 are malicious?

The following RubyGems versions of cwlogs_s3 are flagged malicious: 0.0.6. Treat any of these as compromised.

How do I remediate cwlogs_s3 if I installed it?

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

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

Yes — cwlogs_s3 is associated with the RLMA-2024-05655, RLUA-2024-10174, RLUA-2026-07953 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 cwlogs_s3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cwlogs_s3 (version 0.0.6).

Malicious package

cwlogs_s3RubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in cwlogs_s3 (RubyGems)

MAL-2024-6849

Immediate action

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

gem uninstall cwlogs_s3

Malicious versions

1 flagged

0.0.6

Indicators of compromise (SHA-256)

104e4e6d488037b5d00ad4843d54c652ba5c9df25bb5f5e15d18149cde4bbccc

92231cfef18ddc3f70ac531237304af8e46e89407110b2e1685d1b54737cbaae

733d5da7b9e790012d7f18b65683bd0547e11f35e1b3ae9b39196582ca22491d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05655RLUA-2024-10174RLUA-2026-07953

References

Credits

ReversingLabs · finder

Detect & block this

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