Which versions of zjpage100 are malicious?

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

How do I remediate zjpage100 if I installed it?

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

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

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

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

Malicious package

zjpage100RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9609

Immediate action

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

gem uninstall zjpage100

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9787b5a26afabd705c47f0e34cb9ec1e6456b7f6ddfdb43771480facd7cc6b3a

3a39bfde98a8960c6db46fe2dc797c1cbfb9641a93436e3edc33c3442ae9b1b1

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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