Which versions of wphimp are malicious?

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

How do I remediate wphimp if I installed it?

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

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

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

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

Malicious package

wphimpRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9438

Immediate action

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

gem uninstall wphimp

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d005cd6b245e32a82cbe18e4031c324fe2c016719cd9d542ef8f5663cf1318b5

251b3ed413fb760d8d7359c2bcec9edd9bb327dbb1491afe31822d59a2deaf37

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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