Which versions of swmeet01 are malicious?

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

How do I remediate swmeet01 if I installed it?

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

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

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

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

Malicious package

swmeet01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8946

Immediate action

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

gem uninstall swmeet01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7cef7eaa6b077c5672c511605f2ee791cc5750f0250c00ad5be8788ac13f5654

8984e88376f81086d3b60ac67c5d8d0852befba093515041cadcd71320d83bbc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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