Which versions of wgsfmore73 are malicious?

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

How do I remediate wgsfmore73 if I installed it?

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

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

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

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

Malicious package

wgsfmore73RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9337

Immediate action

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

gem uninstall wgsfmore73

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ea1b108b5de87d4a5a151cee7ba536d4495fd0d29d97ec574429984d2e4fcca1

f59c5f1f00c03b3f42eb09ecbb5a2f45d97ebfd5f8c106b2da9e22921bf80218

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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