Malware in na-rony-test
The npm package na-rony-test contained malware that could fully compromise any system on which it was installed or running. All secrets and keys on affected systems should be rotated immediately, and the package should be removed.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- na-rony-test
The npm package na-rony-test was found to contain malware. According to the GitHub Advisory (GHSA-ppr7-xf9p-cqpg), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, given the potential for full system compromise.\n\nUsers should assume complete loss of confidentiality and integrity on any system where this package was active.
Indicators of compromise
- Packages
- na-rony-test
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the na-rony-test package from all affected systems
- Perform a full security audit and malware scan on any system that had this package installed
- Review system logs and access logs for any unauthorized activity during the period the package was installed
- Consider the affected system(s) potentially fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-ppr7-xf9p-cqpg · GitHub Advisory Database
Cite this entry
"Malware in na-rony-test." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 8, 2026; last updated July 8, 2026. https://supplychainattack.org/incident/malware-in-na-rony-test-14fwlv
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package - containedcritical
Malicious code in epic-common (npm)
The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package - containedcritical
Malicious code in checkout-desktop-total (npm)
The npm package checkout-desktop-total contained malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under wel1.ru. Any system that imported this package should be considered compromised.
npmCompromised package - resolvedcritical
Malicious code in epic-sso (npm)
The npm package epic-sso was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package