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
Malicious code in bcc-design-icons (npm)
bcc-design-icons@9999.0.0 on npm contains malicious postinstall script that exfiltrates hostname and package name to attacker-controlled IP 91.201.215.48:8000. The package lacks expected icon-library functionality and exhibits characteristics of a dependency-confusion attack targeting internal/private npm installers.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in core-tailwindcss-utility (npm)
core-tailwindcss-utility, an npm package falsely advertised as a Tailwind CSS utility, contains malicious code that fetches and executes arbitrary Node.js code from a remote C2 server. The package includes suspicious dependencies for credential theft and remote communication.
npmCompromised package - resolvedcritical
Malicious code in bcc-design (npm)
bcc-design@9999.0.0 on npm is a dependency-confusion beacon package with no legitimate functionality. Its postinstall script exfiltrates the installer's hostname and system metadata to an attacker-controlled IP endpoint.
npmDependency confusionCompromised package - activecritical
Malware in checkout-mobile-pay-button
The npm package checkout-mobile-pay-button contains malware that provides full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package