Which versions of wpact are malicious?

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

How do I remediate wpact if I installed it?

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

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

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

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

Malicious package

wpactRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9434

Immediate action

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

gem uninstall wpact

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ac2dc9336c85df78e08f667f97217ef013a97d69acc0714964fb5c47755e0f5f

0b7f9be9c2b2bff71a33f3b64f956f5868fac5549073f0da32805529cae437dd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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