Which versions of xjinawand1 are malicious?

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

How do I remediate xjinawand1 if I installed it?

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

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

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

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

Malicious package

xjinawand1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9527

Immediate action

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

gem uninstall xjinawand1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b5fd108a54de2f0abbfe9e953db98aa1aa544a6ba51527244521fcb87ec234cf

bdb652e0d1feb862a3fa7e72af21e79a16aa7e3797f8299eda37f35c74b212b1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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