Which versions of wgsfmore53 are malicious?

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

How do I remediate wgsfmore53 if I installed it?

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

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

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

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

Malicious package

wgsfmore53RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9335

Immediate action

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

gem uninstall wgsfmore53

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

232e95413e2c8cb8f787f44290dcf9c855e11a9dc20e5855e0472a80761f569d

8fcb517db2cbbf8f364a70ad32a34fb70d914c120c1b66776ea88d4e4e0fbb9b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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