Which versions of wjstand are malicious?

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

How do I remediate wjstand if I installed it?

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

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

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

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

Malicious package

wjstandRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9370

Immediate action

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

gem uninstall wjstand

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8886c9e087fe91763c70b054a9f9d72559ee5b9f4d21094430ed331b91adc821

000423d725cbfd57f9cec0d6440e08ee60490af8c917b1cf611c7a4d066d0605

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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