Which versions of wgsfmore13 are malicious?

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

How do I remediate wgsfmore13 if I installed it?

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

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

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

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

Malicious package

wgsfmore13RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9331

Immediate action

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

gem uninstall wgsfmore13

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6d52c03c00515f3bcb1286dfaf15d32cfac3b188520e3ca64e7bc01ccbbc7c98

f2b6f2911cf990c29705fa8ae9ff45773d00d49e2b66ffb019acc47cee9e4e9e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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