Which versions of zjenc82c4d3 are malicious?

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

How do I remediate zjenc82c4d3 if I installed it?

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

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

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

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

Malicious package

zjenc82c4d3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9584

Immediate action

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

gem uninstall zjenc82c4d3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

50a915c19f5e73d14065f0468ab18a6bdcbe9eb9073d7a5db5faf30d2633da18

c0db9fe738a96456adc02d7d7171a90f3c62eb96f1344d873c9bb266672438bd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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