Which versions of wngoscmktfuf are malicious?

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

How do I remediate wngoscmktfuf if I installed it?

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

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

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

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

Malicious package

wngoscmktfufRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9416

Immediate action

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

gem uninstall wngoscmktfuf

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5d8aad6956b9986a4120ad63a577a0eb27224e4079a253682017e38a26acac92

085407fafb441759e0154d9538c7d0beba20f1afebf77e4b4ff9b0728f4e5946

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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