Which versions of wjgrants are malicious?

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

How do I remediate wjgrants if I installed it?

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

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

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

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

Malicious package

wjgrantsRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9363

Immediate action

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

gem uninstall wjgrants

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6c235b352526eacc32ebb7335d4fbfe4fbaf9644d95fd492e051ab847f928fe4

e7f959a49757132e18eee34cdc470a3e62bb2bbee0b84dc344e057f2d451b5ff

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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