Which versions of zjfull27888 are malicious?

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

How do I remediate zjfull27888 if I installed it?

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

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

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

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

Malicious package

zjfull27888RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9591

Immediate action

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

gem uninstall zjfull27888

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f48136167d8e77c5600c9e622d2ff84bba74a8ec6856899f3b98d77b0b7618a9

a7bd80a244249cb37a5fbb4c287c8da4523ebea77408d872b1a0a3344237113d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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