Which versions of zjfadgip are malicious?

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

How do I remediate zjfadgip if I installed it?

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

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

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

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

Malicious package

zjfadgipRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9589

Immediate action

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

gem uninstall zjfadgip

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

388864efeff333beddb1b04f5d9a1b97dc4285c6bd7d741e04ecc452bd24128d

3b37126c0b0407dcb04ffd0468972fed8bcdcc3ee933adcf4edb210db54a79ed

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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