Which versions of nwcid320 are malicious?

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

How do I remediate nwcid320 if I installed it?

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

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

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

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

Malicious package

nwcid320RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8144

Immediate action

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

gem uninstall nwcid320

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2f18a006d81410c98eb67c3b32c0a81a851ae433f539fc8c606c28d505b9e2d1

6c597d58a7f81017cb2860106e72b1b09c8d2bbd59e3f49b2eed89d32407a63b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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