Malware in react-native-template-my-starter
Malware was discovered in the npm package react-native-template-my-starter. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- react-native-template-my-starter
A malware-laden version of the npm package react-native-template-my-starter was identified and published to the npm registry. The package provided attackers with full control of affected systems upon installation or execution.\n\nAny computer that has installed or run this package should be considered fully compromised. The advisory recommends immediate rotation of all secrets and keys from a different, unaffected computer. While the package should be removed, complete removal of all malicious artifacts cannot be guaranteed due to the level of system compromise achieved.\n\nThe incident was disclosed via GitHub Advisory GHSA-7p9r-785r-fg9p on 2026-07-06.
Indicators of compromise
- Packages
- react-native-template-my-starter
Remediation
- Immediately remove the react-native-template-my-starter package from all affected systems
- Rotate all secrets, API keys, credentials, and authentication tokens from a different, unaffected computer
- Perform a full security audit and malware scan of any system that had this package installed or running
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-7p9r-785r-fg9p · GitHub Advisory Database
Cite this entry
"Malware in react-native-template-my-starter." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-react-native-template-my-starter-1howwa
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 autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting