Malware in scandoc-scandoc-core
Malware was discovered in the npm package scandoc-scandoc-core. Systems with this package installed or running are 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
- scandoc-scandoc-core
A malicious package named scandoc-scandoc-core was published to npm. According to the GitHub Advisory (GHSA-rv57-q2q4-h6x4), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain attack through a malicious npm package with full system compromise capabilities.
Indicators of compromise
- Packages
- scandoc-scandoc-core
Remediation
- Immediately isolate any computer with scandoc-scandoc-core installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the scandoc-scandoc-core package from all affected systems
- Perform a full security audit and malware scan of affected systems
- Review system logs and access patterns for signs of unauthorized activity
- Consider full system reimaging if compromise is confirmed
Sources
- GitHub Advisory GHSA-rv57-q2q4-h6x4 · GitHub Advisory Database
Cite this entry
"Malware in scandoc-scandoc-core." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-scandoc-scandoc-core-7npf6b
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 @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 - 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 - activecritical
Malware in @sdgdfgdfhhhfd/multiviewr
Malware discovered in the npm package @sdgdfgdfhhhfd/multiviewr. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - 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