Malicious code in @amedit/vercel-builder-probe (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7fe0b29ddff65cbd65167ea905c448d928fc6da661d69df415993635bf1bd3bc) When wired in as a @vercel/build-utils Builder and the exported build() runs in a Vercel deployment pipeline, index.js reads the installer's RUNTIME_CACHE_HEADERS, VERCEL_DEPLOYMENT_KEY, and VERCEL_OIDC_TOKEN environment variables and prints the raw JWTs and deployment key to the build log via console.log lines prefixed '[P1216]' (index.js:21-24). It then HMAC-signs a forged JWT using the installer's VERCEL_DEPLOYMENT_KEY (`crypto.createHmac('sha256', rawKey).update(header+'.'+payload).digest('base64url')`, index.js:41-44) and sends a request carrying that forged token to iad1.suspense-cache.vercel-infra.com with hardcoded team/project/deployment identifiers belonging to a third party. Installer harm is twofold: (1) the deployment key and cache JWT are written into Vercel build logs, where they may be retained, surfaced in CI artifacts, or shared; and (2) the installer's Vercel account is the one issuing a signature-forging request against Vercel's internal suspense-cache endpoint with another party's IDs, exposing the installer to abuse-policy enforcement. The '[P1216]' tag and hardcoded foreign deployment IDs indicate a research/abuse probe rather than a legitimate Builder. ## Source: ghsa-malware (e149c5b37214e25d4fd07a318603e2b499d5a89bbcecd17d7c03b46eb58b70aa) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The @amedit/vercel-builder-probe npm package has been identified as containing malicious code that results in a full system compromise upon installation or execution. This compromise potentially grants an attacker complete control over the affected computer, including access to stored secrets and keys. Due to the severity of the compromise, simply uninstalling the package may not fully remediate the infection, as additional malicious software could have been installed. The advisory recommends immediate rotation of all secrets and keys from a different, uncompromised machine and removal of the package from the affected system.
Potential Impact
Any computer with the @amedit/vercel-builder-probe package installed or running should be considered fully compromised. This includes potential unauthorized access to all secrets and keys stored on the system. The attacker may have persistent control, and the system integrity cannot be guaranteed even after package removal.
Mitigation Recommendations
Remove the @amedit/vercel-builder-probe package immediately from all affected systems. Rotate all secrets and keys stored on the compromised computer from a separate, secure device. Because full system compromise is possible, consider rebuilding or thoroughly cleaning affected systems to ensure removal of all malicious components. No official patch or fix is available; remediation relies on removal and secret rotation.
Malicious code in @amedit/vercel-builder-probe (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7fe0b29ddff65cbd65167ea905c448d928fc6da661d69df415993635bf1bd3bc) When wired in as a @vercel/build-utils Builder and the exported build() runs in a Vercel deployment pipeline, index.js reads the installer's RUNTIME_CACHE_HEADERS, VERCEL_DEPLOYMENT_KEY, and VERCEL_OIDC_TOKEN environment variables and prints the raw JWTs and deployment key to the build log via console.log lines prefixed '[P1216]' (index.js:21-24). It then HMAC-signs a forged JWT using the installer's VERCEL_DEPLOYMENT_KEY (`crypto.createHmac('sha256', rawKey).update(header+'.'+payload).digest('base64url')`, index.js:41-44) and sends a request carrying that forged token to iad1.suspense-cache.vercel-infra.com with hardcoded team/project/deployment identifiers belonging to a third party. Installer harm is twofold: (1) the deployment key and cache JWT are written into Vercel build logs, where they may be retained, surfaced in CI artifacts, or shared; and (2) the installer's Vercel account is the one issuing a signature-forging request against Vercel's internal suspense-cache endpoint with another party's IDs, exposing the installer to abuse-policy enforcement. The '[P1216]' tag and hardcoded foreign deployment IDs indicate a research/abuse probe rather than a legitimate Builder. ## Source: ghsa-malware (e149c5b37214e25d4fd07a318603e2b499d5a89bbcecd17d7c03b46eb58b70aa) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @amedit/vercel-builder-probe npm package has been identified as containing malicious code that results in a full system compromise upon installation or execution. This compromise potentially grants an attacker complete control over the affected computer, including access to stored secrets and keys. Due to the severity of the compromise, simply uninstalling the package may not fully remediate the infection, as additional malicious software could have been installed. The advisory recommends immediate rotation of all secrets and keys from a different, uncompromised machine and removal of the package from the affected system.
Potential Impact
Any computer with the @amedit/vercel-builder-probe package installed or running should be considered fully compromised. This includes potential unauthorized access to all secrets and keys stored on the system. The attacker may have persistent control, and the system integrity cannot be guaranteed even after package removal.
Mitigation Recommendations
Remove the @amedit/vercel-builder-probe package immediately from all affected systems. Rotate all secrets and keys stored on the compromised computer from a separate, secure device. Because full system compromise is possible, consider rebuilding or thoroughly cleaning affected systems to ensure removal of all malicious components. No official patch or fix is available; remediation relies on removal and secret rotation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10548
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-wvc3-vq7q-w2mw"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff6e68715ace432f21e7
Added to database: 07/14/2026, 09:20:46 UTC
Last enriched: 07/14/2026, 09:36:07 UTC
Last updated: 07/30/2026, 08:09:25 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.