Malware in create-remotion
Malware was discovered in the create-remotion npm package. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- create-remotionnpm package
A critical malware incident was identified in the create-remotion npm package. According to the GitHub Advisory (GHSA-947j-5gjp-7968), any system that has installed or executed this package should be treated as fully compromised.\n\nThe advisory indicates that all secrets, keys, and credentials stored on affected computers must be rotated immediately from a separate, uncompromised system. While the malicious package should be removed, the advisory notes that full system compromise may have occurred, meaning removal of the package alone may not eliminate all malicious software that was installed as a result.\n\nThe incident was published on July 31, 2026, and affects the create-remotion package in the npm ecosystem.
Indicators of compromise
- Packages
- create-remotion
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the create-remotion package from all affected systems
- Conduct a full security audit and malware scan of any system that had the 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 systems are involved
Sources
- GitHub Advisory GHSA-947j-5gjp-7968 · GitHub Advisory Database
Cite this entry
"Malware in create-remotion." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 31, 2026; last updated July 31, 2026. https://supplychainattack.org/incident/malware-in-create-remotion-1htir6
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 @404c3s4r/lodash
Malware was discovered in the npm package @404c3s4r/lodash. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in ai-backup-script
The npm package ai-backup-script contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in smart-npv-mcp
The npm package smart-npv-mcp contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in polyprompt
Malware was discovered in the npm package polyprompt, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package