Which versions of zjiatxt1 are malicious?

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

How do I remediate zjiatxt1 if I installed it?

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

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

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

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

Malicious package

zjiatxt1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9602

Immediate action

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

gem uninstall zjiatxt1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

33b1f14e6b584566e0e448913b1ade794f47d05a46bb1ef5ef57e5b22bfbf0d2

f546adf23f772ef4fdf575de262c3b6ff635e0529fe31c205e73cfe2019dbd0d

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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