Which versions of xjinasouth1 are malicious?

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

How do I remediate xjinasouth1 if I installed it?

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

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

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

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

Malicious package

xjinasouth1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9526

Immediate action

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

gem uninstall xjinasouth1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

95fb837e23ca059cc51fdc52ecdc06cc89b74a576fa3be9cf9f23d5ee1d89d64

f1440d89a3702f621840d0752a92375fa6f36d37159d2c97fd3d4a0c67f91ea5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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