MalwarePublished 4 Nov 2026

nannnnnnnnn (npm) · Malicious Code

Affects nannnnnnnnnSource GCVE Database

Malicious package : remove nannnnnnnnn and rotate any secrets on hosts that installed it.

Data as of 5 Nov 2026, 02:45 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-18655

What to do

Remove nannnnnnnnn from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmnannnnnnnnn	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package 'nannnnnnnnn' contains malicious code that compromises any computer on which it is installed or running. Installation of this package may result in full system compromise, including unauthorized access to secrets and keys stored on the affected machine. Immediate removal of the package is recommended, but due to potential full control by an attacker, removal alone may not eliminate all malicious components.

Impact

Full system compromise on any computer with the 'nannnnnnnnn' package installed. Potential exposure and theft of all secrets and keys stored on the compromised machine. The attacker may maintain persistent control beyond the presence of the package itself.

Defensive guidance

Remove the 'nannnnnnnnn' package immediately from affected systems. Rotate all secrets and keys from a separate, secure computer to prevent unauthorized access. Due to the possibility of persistent compromise, consider full system remediation or rebuild to ensure complete removal of malicious components.

Summary

The 'nannnnnnnnn' package on npm is identified as malicious software. According to the source, any system with this package installed should be considered fully compromised. Attackers may have gained full control over the affected system, risking exposure of stored secrets and keys. The recommended response is to rotate all secrets and keys from a different, uncompromised system and to remove the malicious package. However, removal of the package does not guarantee eradication of all malicious software introduced by the compromise.

References

github.com/advisories/GHSA-hqfx-x4m7-grcv (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 02:45 UTC

Technical details

References

Community reviews