Which versions of nwcid315 are malicious?

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

How do I remediate nwcid315 if I installed it?

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

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

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

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

Malicious package

nwcid315RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8140

Immediate action

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

gem uninstall nwcid315

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6dea0e93151000538588e3bb7c2ab4147c58462bfd05a1bfbc92cd3c70ab4005

db02b5bc8caeecd1402b4c3a81529c4a67b41d83f822e7db02ecf17d931d7bd1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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