Which versions of wwagenda2601simpb are malicious?

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

How do I remediate wwagenda2601simpb if I installed it?

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

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

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

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

Malicious package

wwagenda2601simpbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9491

Immediate action

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

gem uninstall wwagenda2601simpb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

047ebf1baa00a59545d2995c2a19a318ac5324457fddae2175bcbc8092923e32

0cd21e005efc3b00e25a93a08040614f6921114e962260982cebff226f9b4982

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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