Which versions of zjpage50 are malicious?

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

How do I remediate zjpage50 if I installed it?

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

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

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

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

Malicious package

zjpage50RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9612

Immediate action

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

gem uninstall zjpage50

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6cb1721b9fbf61a3673eb1195c8d07b56da2a1ff2b7981d9c25b644c8f19581f

dda937b47eec8637564e4743458f3a4fbc9c30e9b0fd566d5a19838ed61797f1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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