Which versions of zjpage5 are malicious?

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

How do I remediate zjpage5 if I installed it?

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

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

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

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

Malicious package

zjpage5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9611

Immediate action

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

gem uninstall zjpage5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

548d84c64b908ba5ef88bbf7402ba83ca7d0e043276bdd9b2283eb4b961012c5

a9b3e57dfc95c4cf7e245f4ff55f19c86fdbfd5634e10fe58ac3bfbbf998611b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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