Which versions of wnkbnefoxjyr are malicious?

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

How do I remediate wnkbnefoxjyr if I installed it?

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

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

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

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

Malicious package

wnkbnefoxjyrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9418

Immediate action

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

gem uninstall wnkbnefoxjyr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ed388d067ee168d9484ab0dc433313f847bda7f01a90e9c2a5cb6baf588f3412

33e7f3af9a201ab636d10bb497a4d14db4ff1146e5bde3b8f0f1cea57ed09d17

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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