Which versions of znowflake_client are malicious?

The following RubyGems versions of znowflake_client are flagged malicious: 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 2.0.0, 2.1.0. Treat any of these as compromised.

How do I remediate znowflake_client if I installed it?

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

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

Yes — znowflake_client is associated with the RLMA-2024-10375, RLUA-2024-11218, RLUA-2026-10254 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 znowflake_client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for znowflake_client (11 malicious versions).

Malicious package

znowflake_clientRubyGems

Advisory published Oct 16, 2024Updated Sep 24, 2026

znowflake_client is a confirmed malicious RubyGems package (MAL-2024-10224) that executes malicious code on install (malicious versions 1.1.1, 1.1.2, 1.1.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in znowflake_client (RubyGems)

MAL-2024-10224

Immediate action

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

gem uninstall znowflake_client

Malicious versions

11 flagged

1.1.11.1.21.1.31.1.41.1.51.1.61.1.71.1.81.1.92.0.02.1.0

Indicators of compromise (SHA-256)

3cfea6ca7519bc610003f8cc86f57732ae75ecc8fe7c093a242f67c250d6d1e6

68dac0e7a16edcb59cf6c6606310372de40db78b2501b9227e7d80434c2530af

e0b3915d33258c430eeda400e8d9799916140c16894b00205c7277d83eafa5cd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for znowflake_client (11 malicious versions).
If you installed it — respond
Remove znowflake_client 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 znowflake_client 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. znowflake_client on RubyGems has been identified as a malicious package (versions 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-10375RLUA-2024-11218RLUA-2026-10254

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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