Which versions of nwcid311 are malicious?

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

How do I remediate nwcid311 if I installed it?

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

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

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

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

Malicious package

nwcid311RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8139

Immediate action

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

gem uninstall nwcid311

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d8c65a0360fb027e676b8161f11db964553bdba4383edf9e280b6647492b5675

d4ad1fbd030e7725c411d78f6057758429ddd36f0701753b8c8da638698479b4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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