Which versions of woppwyijhxfak are malicious?

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

How do I remediate woppwyijhxfak if I installed it?

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

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

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

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

Malicious package

woppwyijhxfakRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9423

Immediate action

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

gem uninstall woppwyijhxfak

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e184f0f54928ccceca6b310fbe06b28e7c183f084f0b8a0c818ed06f384d41fd

4da811008054636c28aa5ec25b01f6dc451a02be3390b9048138b1ed88baecc1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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