Which versions of zjencba0ca4 are malicious?

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

How do I remediate zjencba0ca4 if I installed it?

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

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

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

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

Malicious package

zjencba0ca4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9586

Immediate action

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

gem uninstall zjencba0ca4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

609d4caa089c4914eb721db215d229ba699152a264a52ecd57ce9e617d13f493

093cf826af7376aaf13dbad236e05f2130e74d3788bcc533c5cc05ba0c5ec6cf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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