Malware in rebrandly-domains-digger
Malware was discovered in the npm package rebrandly-domains-digger, resulting in full system compromise for any computer with the package installed or running. The advisory recommends immediate removal of the package and rotation of all secrets and keys from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- rebrandly-domains-digger
A critical malware incident was identified in the npm package rebrandly-domains-digger. According to the GitHub Security Advisory (GHSA-44wx-4683-p2h3), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malicious package grants outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected computer.\n\nWhile removal of the package is recommended, the advisory notes that full control may have been given to an outside entity, meaning there is no guarantee that package removal will eliminate all malicious software resulting from the installation.
Indicators of compromise
- Packages
- rebrandly-domains-digger
Remediation
- Immediately remove the rebrandly-domains-digger package from all systems
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Assume full system compromise and conduct forensic analysis
- Review system logs for unauthorized access or activity
- Consider full system reimaging if sensitive data was present
Sources
- GitHub Advisory GHSA-44wx-4683-p2h3 · GitHub Advisory Database
Cite this entry
"Malware in rebrandly-domains-digger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-rebrandly-domains-digger-f1pfjs
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 awaitly-libsql
The npm package awaitly-libsql was found to contain malware. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
npmCompromised package - containedcritical
Malware in autotel-mcp-instrumentation
Malware was discovered in the npm package autotel-mcp-instrumentation. 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 - activecritical
Malware in autotel-pact
The npm package autotel-pact 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 - containedcritical
Malware in autotel-playwright
Malware was discovered in the npm package autotel-playwright. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package