Which versions of wp925 are malicious?

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

How do I remediate wp925 if I installed it?

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

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

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

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

Malicious package

wp925RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9431

Immediate action

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

gem uninstall wp925

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8763604c57ed2525921a917bf0c9f3093d5b72c55580e9aa67ca5532a587d503

506bb61babff95577449c97075edf97c2e37e590610f8c49e61848fbbce764de

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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