Which versions of wjcab are malicious?

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

How do I remediate wjcab if I installed it?

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

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

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

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

Malicious package

wjcabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9362

Immediate action

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

gem uninstall wjcab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d3ad7670505e5b0ec46bfb427c4a5308835ef69358e5b7bde340739cbc9b674a

8aad09dccc8bb6dcb2d42e388d6ff2bf747ff2b0d7e47cf9e5ce968a485d04cc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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