Which versions of no6gg are malicious?

The following npm versions of no6gg are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10. Treat any of these as compromised.

How do I remediate no6gg if I installed it?

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

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

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

Search your lockfiles and build artifacts for no6gg (11 malicious versions).

Malicious package

no6ggnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

no6gg is a confirmed malicious npm package (MAL-2026-1801) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in no6gg (npm)

MAL-2026-1801

Immediate action

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

npm uninstall no6gg

What this malware does

The package no6gg was found to contain malicious code.

Malicious versions

11 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.10

Indicators of compromise (SHA-256)

3edf2a321872607604c0c9b8e0e32a8829e1f91c77c539737265f92c654a5271

9a9d39f8e57b956b336c3e18782f10c7173ea316513199f85be395fd80cda095

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for no6gg (11 malicious versions).
If you installed it — respond
Remove no6gg 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 no6gg 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. no6gg on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01455

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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