Which versions of wgssrftest are malicious?

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

How do I remediate wgssrftest if I installed it?

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

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

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

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

Malicious package

wgssrftestRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9352

Immediate action

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

gem uninstall wgssrftest

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6cf4a16a59dc48212a436467633f3992260007fee765f9a6e7dd4d62521e2f2d

22e6212e99f3dab5c04f57d3af1b8263438727c6cb3886ad2b389c4c694bb1e2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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