Which versions of wgsfx03 are malicious?

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

How do I remediate wgsfx03 if I installed it?

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

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

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

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

Malicious package

wgsfx03RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9346

Immediate action

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

gem uninstall wgsfx03

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a98dadabf69aaa621088626acf07f92a8f732e290945ac8161d50c78d0a2e98a

b981e2c9029a66002536cab4075bd6a9b0bb6a714af48958a9b27f4845055af3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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