Which versions of wgsfostrail2 are malicious?

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

How do I remediate wgsfostrail2 if I installed it?

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

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

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

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

Malicious package

wgsfostrail2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9345

Immediate action

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

gem uninstall wgsfostrail2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3c167fbfee319a0dd038010eba287b5f156adc958ab9f9548950a9694995624d

d29e35fd336c8745f47b8ede68919a230b3640f0257037cae5134becceb885be

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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