Which versions of wjin4 are malicious?

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

How do I remediate wjin4 if I installed it?

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

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

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

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

Malicious package

wjin4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9367

Immediate action

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

gem uninstall wjin4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0f21784f52eae8f7474344c5943b56bb68b97d996d1de4ecc7042ce2cf3e6e26

295801c99f37f2096d401deadb6f379148f35b9857a88d115571badad1f7a940

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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