Which versions of fluent-plugin-container-logs_filter are malicious?

The following RubyGems versions of fluent-plugin-container-logs_filter are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate fluent-plugin-container-logs_filter if I installed it?

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

If fluent-plugin-container-logs_filter 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 fluent-plugin-container-logs_filter part of a known attack campaign?

Yes — fluent-plugin-container-logs_filter is associated with the RLMA-2024-05703, RLUA-2024-10222, RLUA-2026-08085 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 fluent-plugin-container-logs_filter across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fluent-plugin-container-logs_filter (version 0.0.4).

Malicious package

fluent-plugin-container-logs_filterRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

fluent-plugin-container-logs_filter is a confirmed malicious RubyGems package (MAL-2024-6897) 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 fluent-plugin-container-logs_filter (RubyGems)

MAL-2024-6897

Immediate action

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

gem uninstall fluent-plugin-container-logs_filter

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

e6607bdb42d003719a68581f1b25768b7f65c7c2d8f2322ab126dcbf85824c46

19e56621e8fc86e2cfa8a02d6915b32c7b675918414f229ced0650a7d0d906ad

3201ef1397dd4720a8e812c5268955cc90c9590487908ac7824f67e9ff927662

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for fluent-plugin-container-logs_filter (version 0.0.4).
If you installed it — respond
Remove fluent-plugin-container-logs_filter 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 fluent-plugin-container-logs_filter 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. fluent-plugin-container-logs_filter 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-05703RLUA-2024-10222RLUA-2026-08085

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks fluent-plugin-container-logs_filter-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