Which versions of liquid-renderer are malicious?

The following RubyGems versions of liquid-renderer are flagged malicious: 5.0.1. Treat any of these as compromised.

How do I remediate liquid-renderer if I installed it?

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

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

Yes — liquid-renderer is associated with the RLMA-2024-05764, RLUA-2024-10284, RLUA-2026-08492 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 liquid-renderer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for liquid-renderer (version 5.0.1).

Malicious package

liquid-rendererRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in liquid-renderer (RubyGems)

MAL-2024-6958

Immediate action

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

gem uninstall liquid-renderer

Malicious versions

1 flagged

5.0.1

Indicators of compromise (SHA-256)

01f64c50ab7d1c4949d1cd972338b18609bc6eff7a167dd976ce1e6edc919aa7

54be96b2fe91ee31beaa6bc5baaf29fe266223825447b60208025e4cdf962247

9e47b22ddb514c3bd4f7c17f6d0435863465df55e28d8dd8a8edd1b29d4c5115

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05764RLUA-2024-10284RLUA-2026-08492

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks liquid-renderer-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