Which versions of wjin3 are malicious?

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

How do I remediate wjin3 if I installed it?

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

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

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

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

Malicious package

wjin3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9366

Immediate action

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

gem uninstall wjin3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f1dab0052a4ce99a5b746743c9ad6720d22c4a3e6df0ad22996b6af73c714194

fb1cffbdcc6da8ccdc0ed31b7b7f16abcbd31e1b7f7126621d0075573e14d5ad

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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