na-rony (npm) · Malicious Code
Affects na-ronySource GCVE Database
Malicious package : remove na-rony and rotate any secrets on hosts that installed it.
Data as of 10 Jul 2026, 09:29 UTC
Malicious package
Published to npm · OSV MAL-2026-6964
What to do
Remove na-rony 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 |
|---|---|---|
| npmna-rony | Affected– | Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (193f3dbfb6073e7b6c5dacb0e79157ccac9c69ac4c23d2c8270cc23d27cab699) package.json declares `postinstall: node index.js`, causing index.js to execute automatically on `npm install`. The script collects the installer's OS username (os.userInfo().username), current working directory (process.cwd()), hostname (os.hostname()), and non-internal IPv4 address (derived from os.networkInterfaces()), then POSTs them as a JSON body to a hardcoded webhook.site endpoint controlled by the author. The package has no legitimate library functionality — its only file is the beacon, its description is empty, and it declares a self-referential dependency on itself. Installing this package leaks installer host identifiers to an attacker-controlled collector. ## Source: ghsa-malware (6683e1e146d2ae7fca2a8b56fa91303c99ba4425e55da9863640a09961796805) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.