Which versions of zexcoknh41ysf13 are malicious?

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

How do I remediate zexcoknh41ysf13 if I installed it?

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

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

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

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

Malicious package

zexcoknh41ysf13RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9565

Immediate action

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

gem uninstall zexcoknh41ysf13

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1edb72a91d8e718704a773b8b9f71df229864f28b483bd05d0f2d8e11a4cfbbb

88feaaf14f36b08723c2cc22110194dfcf008b01f9379940d133624cbf88961b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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