Which versions of wgsfmore43 are malicious?

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

How do I remediate wgsfmore43 if I installed it?

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

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

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

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

Malicious package

wgsfmore43RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9334

Immediate action

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

gem uninstall wgsfmore43

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e9ed66bcdae7f43d7a7c0fbec2011d8d8beac827809cecf4c983a7aff9490f82

57e450eb0a2f0ccfc27db1f0e77a2bc49b806d7242e0ea93c3ab9a5ab68da2ee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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