Which versions of zjapiq55 are malicious?

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

How do I remediate zjapiq55 if I installed it?

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

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

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

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

Malicious package

zjapiq55RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9581

Immediate action

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

gem uninstall zjapiq55

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

041c8ad99eb76a54a070304414e26be71b0961cc680c145083b26218007621e0

179e449486a3c8e11ab2e4358353f8ed53cb2eab48607b660c00374d2b84eaf0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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