Which versions of zrzjtf016e are malicious?

The following RubyGems versions of zrzjtf016e are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate zrzjtf016e if I installed it?

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

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

Yes — zrzjtf016e is associated with the RLMA-2026-04412, RLUA-2026-10350 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 zrzjtf016e across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zrzjtf016e (version 0.0.1).

Malicious package

zrzjtf016eRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zrzjtf016e is a confirmed malicious RubyGems package (MAL-2026-9761) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zrzjtf016e (RubyGems)

MAL-2026-9761

Immediate action

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

gem uninstall zrzjtf016e

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

648554f062e75819f402cf65ca7c86c2e98106b4926e5b5da5facb8d08f5def2

2c56347d703a768c0c32511b7f89aed104408ae788904f40016697474f633aee

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04412RLUA-2026-10350

References

Credits

ReversingLabs · finder

Detect & block this

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