Which versions of wgsfmore83 are malicious?

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

How do I remediate wgsfmore83 if I installed it?

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

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

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

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

Malicious package

wgsfmore83RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9338

Immediate action

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

gem uninstall wgsfmore83

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2337f003d121d04ef03e501ed0b2370faf90d8e74697adb9af9a7f72f3c0690f

09143922d08938b609c97c98259a35ed2c1b1e916d0eeb9f29c90b200f9f61e6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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