Which versions of zswmeetxml28208 are malicious?

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

How do I remediate zswmeetxml28208 if I installed it?

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

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

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

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

Malicious package

zswmeetxml28208RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9803

Immediate action

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

gem uninstall zswmeetxml28208

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2581624a23453c9c057b1e1958d2f7bcef13573e12a5836977ef66980cdd33de

2293a269dcdf5fdf061e572f76417756af525bd8c9afabc95135d2da6fb2fef9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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