Which versions of wgsfmore23 are malicious?

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

How do I remediate wgsfmore23 if I installed it?

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

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

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

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

Malicious package

wgsfmore23RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9332

Immediate action

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

gem uninstall wgsfmore23

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0dc7f94c6ad547aafb324713b34a8ab2770fef95172c91436ec60a37b4e5b630

3bfc93d0fafbc51a26c9e189a9a13a4779aad8b002df5c50a43969f17d363e85

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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