Which versions of zen-ruby-linter are malicious?

The following RubyGems versions of zen-ruby-linter are flagged malicious: 1.8.1. Treat any of these as compromised.

How do I remediate zen-ruby-linter if I installed it?

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

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

Yes — zen-ruby-linter is associated with the RLMA-2024-10374, RLUA-2024-11217, RLUA-2026-10151 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 zen-ruby-linter across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zen-ruby-linter (version 1.8.1).

Malicious package

zen-ruby-linterRubyGems

zen-ruby-linter is a confirmed malicious RubyGems package (MAL-2024-10223) that executes malicious code on install (malicious version 1.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zen-ruby-linter (RubyGems)

MAL-2024-10223

Immediate action

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

gem uninstall zen-ruby-linter

Malicious versions

1 flagged

1.8.1

Indicators of compromise (SHA-256)

f7221480a31b3e28d8d6487a1380d4cf770f385000b71529457f7b7b9874aaf2

35f579f16dcc3d719af208f346b492e382176ddbdab88af1de0dc781359a21fd

9ae96dfd5017a7aefd6b9f068b3d17611e3daa72927f8d4fd0b2c8406c55278c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-10374RLUA-2024-11217RLUA-2026-10151

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks zen-ruby-linter-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