Which versions of wgsfoshttp2 are malicious?

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

How do I remediate wgsfoshttp2 if I installed it?

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

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

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

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

Malicious package

wgsfoshttp2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9340

Immediate action

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

gem uninstall wgsfoshttp2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fc03914e70c7e0966ce7f512ce2b9551cf448440744e7ba391ecbe8a364208de

4b27867c2dda679f934ad0d406248d4b0b078e472de5f321747509468314479d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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