Which versions of zjpage2 are malicious?

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

How do I remediate zjpage2 if I installed it?

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

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

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

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

Malicious package

zjpage2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9610

Immediate action

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

gem uninstall zjpage2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9acb5b88f2f3d05dd1a3581867a035637d9a99323c8c4e2ebbda61e0ec7ba426

07e9868ea80088c5476f7873856254ad2d7055f4259a82b5d51ba509280cc543

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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