Which versions of zjinside1 are malicious?

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

How do I remediate zjinside1 if I installed it?

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

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

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

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

Malicious package

zjinside1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9606

Immediate action

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

gem uninstall zjinside1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3c69b95d8e84b5d8b71385284ed56ca6e4e029aba20a142227e25ed9b2e830d3

8d7f1b0f68cfae73f89fae48945d020a9ae7a729cc779b95e50fb3b53a98f28e

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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