Malware in blastradar
Malware was discovered in the npm package blastradar, 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.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- blastradar
The npm package blastradar was found to contain malware. According to the GitHub Advisory (GHSA-pp9x-4g56-7322), any computer that has this package installed or running should be considered fully compromised.\n\nAffected users are advised to rotate all secrets and keys stored on compromised computers immediately from a different, unaffected system. The package should be removed, though full system compromise means there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial package installation.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for complete system takeover.
Indicators of compromise
- Packages
- blastradar
Remediation
- Immediately remove the blastradar package from all systems
- Rotate all secrets, API keys, and credentials from a different, unaffected computer
- Perform a full security audit and malware scan of any system that had blastradar installed
- Review system logs for unauthorized access or activity during the period the package was installed
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-pp9x-4g56-7322 · GitHub Advisory Database
Cite this entry
"Malware in blastradar." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malware-in-blastradar-xdtvf2
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 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package