Which versions of zsvnjin2a18dd are malicious?

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

How do I remediate zsvnjin2a18dd if I installed it?

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

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

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

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

Malicious package

zsvnjin2a18ddRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9792

Immediate action

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

gem uninstall zsvnjin2a18dd

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8a6dbc8f77333b57241eefd9b96ff368daf05931ca299e7f7a4407c7a0839047

c36008edd69ec92c314d8c4be2e991fe93798c1fb613e16250a69042d5f5c439

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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