Which versions of nwcid323 are malicious?

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

How do I remediate nwcid323 if I installed it?

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

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

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

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

Malicious package

nwcid323RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8147

Immediate action

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

gem uninstall nwcid323

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fcd72b8011b639242a3c2c46be6a8da918389b2f2adfb147fc09e568830275ac

1acf7119bbde371155952893ebfd6d4289bf8453969f50cdbaa546f8fee41a64

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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