Which versions of zjfull1 are malicious?

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

How do I remediate zjfull1 if I installed it?

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

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

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

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

Malicious package

zjfull1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9590

Immediate action

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

gem uninstall zjfull1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d4af4a10b44e41589fdbb2b38a307eaea92f2c42ce33142ba42e6d52f0a3c8a7

a0138d93682d089af86e0168de0e16daeeb64c6a92efdcd1d913c032183467cc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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