Which versions of nwcid322 are malicious?

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

How do I remediate nwcid322 if I installed it?

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

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

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

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

Malicious package

nwcid322RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8146

Immediate action

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

gem uninstall nwcid322

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0b9596e61f0bf0b1d819f813fe9072c4f09019e8e9b4b51aa4d3f3b0835192c1

b57c580cda7580ed80b04db7a00b52a9ae5881f4f26d05594c8339e7c312f6c4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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