Which versions of wjlic are malicious?

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

How do I remediate wjlic if I installed it?

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

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

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

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

Malicious package

wjlicRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9368

Immediate action

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

gem uninstall wjlic

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a8240ec8a29438f20f66ac9079299dd1c8d1c0e09bbdade10aa67d9d38928138

37cace188ea28c85b2dc541582d905a2c7b123730d1ad15a879c62814f1ad8c1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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