Malware in rony-testing
The npm package rony-testing contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- rony-testingnpm package containing malware
The npm package rony-testing was found to contain malware. According to the GitHub Advisory (GHSA-7p38-gfgq-g3f3), any computer that has 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 that the attacker may have gained full control of the system.\n\nThis represents a critical supply chain attack through a malicious npm package.
Indicators of compromise
- Packages
- rony-testing
Remediation
- Immediately isolate any computer that has rony-testing installed or running from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the rony-testing package from all systems
- Perform a full security audit and malware scan on affected systems
- Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical systems are involved
- Review access logs and audit trails for any unauthorized activity during the period the package was installed
Sources
- GitHub Advisory GHSA-7p38-gfgq-g3f3 · GitHub Advisory Database
Cite this entry
"Malware in rony-testing." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 8, 2026; last updated July 8, 2026. https://supplychainattack.org/incident/malware-in-rony-testing-18z0ai
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in tailwind-core
Malware was distributed via the npm package tailwind-core. Systems with the package installed are considered fully compromised and require immediate remediation.
npmCompromised package - resolvedcritical
Malware in gas-log
The npm package gas-log contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in na-rony-test-karem
The npm package na-rony-test-karem contains malware that grants full control of affected systems to an outside entity. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in mci-sdk
Malware discovered in the npm package mci-sdk. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package