Which versions of zakoyavnjezx are malicious?

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

How do I remediate zakoyavnjezx if I installed it?

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

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

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

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

Malicious package

zakoyavnjezxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zakoyavnjezx is a confirmed malicious RubyGems package (MAL-2026-9560) 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 zakoyavnjezx (RubyGems)

MAL-2026-9560

Immediate action

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

gem uninstall zakoyavnjezx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0f26b018da479153526d5f907fcd469ab7b2c69d19e1cd22994b7802cf845f98

0d59781e3242d722893a36e12fc3d504e1e6b138e7ad25219c63d5c1b6969d45

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zakoyavnjezx (version 0.0.1).
If you installed it — respond
Remove zakoyavnjezx 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 zakoyavnjezx 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. zakoyavnjezx 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-04211RLUA-2026-10146

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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