Which versions of zjfull3351 are malicious?

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

How do I remediate zjfull3351 if I installed it?

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

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

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

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

Malicious package

zjfull3351RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9592

Immediate action

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

gem uninstall zjfull3351

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6364f60b57b757551374383a2b44171b41a331dbac82963147be65cbcf93e309

f04180dab4afd26e0c747952b915546405d3a65d0c9600fdcb86e5a74a5ca65c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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