Which versions of wwagenda2601abc are malicious?

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

How do I remediate wwagenda2601abc if I installed it?

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

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

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

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

Malicious package

wwagenda2601abcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9490

Immediate action

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

gem uninstall wwagenda2601abc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

de588dad06a0c0a949d2435ace899107e794cacff617978bfc1080e29372bd24

99046e2defe9fbf5e85c10635feea066c4d3e5b4f8568dc6e361cd15e29de5a3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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