Malware in @amedit/vercel-builder-probe
Malware was discovered in the npm package @amedit/vercel-builder-probe. Systems with this package installed 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
- @amedit/vercel-builder-probe
A malicious package named @amedit/vercel-builder-probe was published to npm and contains malware. Any computer that has installed or run this package should be considered fully compromised, with potential for complete system takeover by an external entity.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the package itself should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nThis incident was disclosed via GitHub Advisory GHSA-wvc3-vq7q-w2mw on 2026-07-14.
Indicators of compromise
- Packages
- @amedit/vercel-builder-probe
Remediation
- Immediately remove the @amedit/vercel-builder-probe package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Assume full system compromise and conduct a thorough security audit
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Consider rebuilding affected systems from clean media if critical infrastructure is involved
Sources
- GitHub Advisory GHSA-wvc3-vq7q-w2mw · GitHub Advisory Database
Cite this entry
"Malware in @amedit/vercel-builder-probe." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-amedit-vercel-builder-probe-wgkddy
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 @years17/n8n-nodes-utils-helper-f (npm)
The npm package @years17/n8n-nodes-utils-helper-f contains malicious code in its postinstall script and a node module that performs reconnaissance, exfiltrates system data to a C2 server, and establishes persistent SSH access. The package was identified by OpenSSF's malicious-packages project.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in @years17/n8n-nodes-utils-helper-c (npm)
The npm package @years17/n8n-nodes-utils-helper-c contained malicious code that performed host reconnaissance via a postinstall script and a fake n8n node, exfiltrating system information to an external C2 server. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in @assetshop/verify-cli (npm)
The npm package @assetshop/verify-cli contained malicious code in its preinstall hook that collected and exfiltrated system and user information to an external OAST callback domain. The package exhibited the standard dependency-confusion reconnaissance pattern targeting private registries.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in verify-cli (npm)
The npm package verify-cli version 99.0.0 contained malicious code that exfiltrated system information and sensitive files to an out-of-band endpoint during installation. The package exhibited characteristics of a typosquatting/dependency-confusion attack with implausible metadata.
npmCompromised packageTyposquatting