Which versions of zjenca01b83 are malicious?

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

How do I remediate zjenca01b83 if I installed it?

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

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

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

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

Malicious package

zjenca01b83RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9585

Immediate action

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

gem uninstall zjenca01b83

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ed871774899779551fe4944e45cf071e90b60b9d11298fec573dc788f643698e

2d016a2d60d7762bfff66a2f13c23b7ba8424aca64756af806afe5951839d89c

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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