Which versions of wpfox are malicious?

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

How do I remediate wpfox if I installed it?

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

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

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

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

Malicious package

wpfoxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9436

Immediate action

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

gem uninstall wpfox

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

448819d9be994fce6154572124ce356406c2946093ff00a858d565b3632782de

8b17ff74c05dcf3c03e217d0b3aebfe0ab0a37a1ecde8c61940a611f31bab6b4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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