Which versions of zjenc31c8c8 are malicious?

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

How do I remediate zjenc31c8c8 if I installed it?

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

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

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

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

Malicious package

zjenc31c8c8RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9583

Immediate action

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

gem uninstall zjenc31c8c8

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3b8bec25d0560bfb162039bb5ff07b2038333d82b3a4dbccf652f213cdcdc6a7

ab00dea64822de3f986c38d72fa3e57e617247f70f7ce131ae374514e4f22043

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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