Which versions of wphraA are malicious?

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

How do I remediate wphraA if I installed it?

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

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

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

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

Malicious package

wphraARubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9442

Immediate action

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

gem uninstall wphraA

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

11cd6fd8e9d871e209b17101c8375484af60a5f4b641a4720a1ba1c6f31d08b1

284d6145dd2e07b421554807f1dd503fdf444fbd9457cb82a194239350eea991

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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