Which versions of nwcid324 are malicious?

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

How do I remediate nwcid324 if I installed it?

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

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

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

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

Malicious package

nwcid324RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8148

Immediate action

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

gem uninstall nwcid324

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

00a65633af298d57d07f0954fed4d7759f6569fdd9508ee8572c9b32c59101d6

7f30ae2f1bd878dc2a957161b96d62dcaaa73d97aeac9f0d556698ad199049cc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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