Which versions of wjin1 are malicious?

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

How do I remediate wjin1 if I installed it?

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

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

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

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

Malicious package

wjin1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9364

Immediate action

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

gem uninstall wjin1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b67ad1b6f2f4e5bafa533e8ceb4a50a476b370af194255f161cd0b3793a7ff72

f38fac32df370ef8cb07f70ef694e39a9605b20c046325616be49fa39d963afe

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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