Incident Score: Analysis & Impact (VER1776772360)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Vercel's Breach and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Vercel Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Vercel breach identified under incident ID VER1776772360.
The analysis begins with a detailed overview of Vercel's information like the linkedin page: https://www.linkedin.com/company/vercel, the number of followers: 200744, the industry type: Software Development and the number of employees: 873 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 762 and after the incident was 702 with a difference of -60 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Vercel and their customers.
Vercel recently reported "Vercel Breach Exposes Customer Credentials via Third-Party AI Tool", a noteworthy cybersecurity incident.
Cloud hosting platform Vercel recently disclosed a security breach stemming from a compromised third-party AI tool.
The disruption is felt across the environment, affecting Internal systems, third-party OAuth app, and exposing Customer credentials, employee accounts, API keys (NPM, GitHub tokens), source code.
In response, moved swiftly to contain the threat with measures like Additional security measures and monitoring implemented, and stakeholders are being briefed through Public disclosure of breach.
The case underscores how teams are taking away lessons such as Growing risk of supply chain compromises targeting developer tools and third-party integrations; need for stricter OAuth app vetting and monitoring, and recommending next steps like Implement stricter third-party integration policies, enhance OAuth app security reviews, and improve monitoring for unauthorized access, with advisories going out to stakeholders covering Affected customers were contacted; others were assured they were unaffected.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), supported by evidence indicating employee connected a Google Workspace OAuth app to their corporate account and Supply Chain Compromise: Compromise Software Supply Chain (T1195.002) with moderate to high confidence (80%), supported by evidence indicating compromised third-party AI tool allowed threat actors to access internal systems. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (90%), supported by evidence indicating google Workspace OAuth app compromised, exposing credentials and Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (80%), supported by evidence indicating aPI keys (including NPM and GitHub tokens) were accessed. Under the Lateral Movement tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (80%), supported by evidence indicating threat actors accessed internal systems via compromised OAuth app. Under the Collection tactic, the analysis identified Data from Cloud Storage (T1530) with moderate to high confidence (80%), supported by evidence indicating source code and API keys were accessed and stolen and Data from Code Repositories (T1213.003) with moderate to high confidence (70%), supported by evidence indicating gitHub tokens and source code were compromised. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating stolen data is reportedly being sold on hacking forums. Under the Impact tactic, the analysis identified Account Access Removal (T1531) with moderate confidence (50%), supported by evidence indicating vercel implemented additional security measures post-breach. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Vercel Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/vercel/incident/VER1776772360
- Vercel CyberSecurity Rating page: https://www.rankiteo.com/company/vercel
- Vercel Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/ver1776772360-vercel-breach-january-2025/
- Vercel CyberSecurity Score History: https://www.rankiteo.com/company/vercel/history
- Vercel CyberSecurity Incident Source: https://tech.co/news/app-host-vercel-hack-ai-tool
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf