Which versions of wwagenda2601txtab are malicious?

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

How do I remediate wwagenda2601txtab if I installed it?

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

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

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

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

Malicious package

wwagenda2601txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9492

Immediate action

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

gem uninstall wwagenda2601txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bd12769e87a0fc5bea99151df558b67ce9b4f21aa3ead33905602bf9b271196f

4f1705c41c84debca5fe268ca9689f3df7ab0910f562e62b69b063397227fae9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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