Which versions of nwcid318 are malicious?

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

How do I remediate nwcid318 if I installed it?

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

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

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

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

Malicious package

nwcid318RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8142

Immediate action

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

gem uninstall nwcid318

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

252345eabd493b1fa6859aca1ef2876603f7c68d3f3642b8ae5305fbf53a0d51

c4311552fd40aabcaa818652299144be9d0892eebab9b9468ecc0b7c0a4489b6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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