Which versions of zsmeet018652 are malicious?

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

How do I remediate zsmeet018652 if I installed it?

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

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

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

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

Malicious package

zsmeet018652RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9790

Immediate action

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

gem uninstall zsmeet018652

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

df0ca55ca8c2f96b63a2b24675bc44a77695b362aa76b0fc030712af9e84e9e6

7a4c8a3bd03e2aa068cc85aca7401558d8feb65a240814501c0bb09554ab4008

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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