Incident Score: Analysis & Impact (ADOSTRGOO1780611936)
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 Stripe's Cyber Attack 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 Stripe 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 Stripe breach identified under incident ID ADOSTRGOO1780611936.
The analysis begins with a detailed overview of Stripe's information like the linkedin page: https://www.linkedin.com/company/stripe, the number of followers: 1266824, the industry type: Technology, Information and Internet and the number of employees: 14133 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 783 and after the incident was 768 with a difference of -15 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 Stripe and their customers.
On 24 December 2025, a cybersecurity incident called "New Magecart Campaign Exploits Stripe API to Steal Payment Data" came to light.
Researchers at Sansec have uncovered a sophisticated Magecart campaign leveraging Stripe’s API infrastructure and Google Tag Manager (GTM) to steal credit card details from e-commerce checkout pages.
The disruption is felt across the environment, affecting Magento/Adobe Commerce e-commerce stores, and exposing Credit card details (number, CVV, expiration date), billing information, customer contact data.
Formal response steps have not been shared publicly yet.
The case underscores how Ongoing (research phase), teams are taking away lessons such as Threat actors are increasingly abusing trusted third-party services (e.g., Stripe, Google Tag Manager) to bypass security controls. Strict content security policies (CSP) and monitoring of outbound API traffic are critical to detecting such attacks, and recommending next steps like Implement strict Content Security Policies (CSP) to restrict unauthorized script execution, Monitor outbound API traffic for anomalies, especially to payment processors like Stripe and Audit Google Tag Manager (GTM) containers for unauthorized scripts.
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 Supply Chain Compromise: Compromise Software Supply Chain (T1195.002) with high confidence (90%), with evidence including compromised Google Tag Manager (GTM) containers, and supply chain such as true. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: JavaScript (T1059.007) with moderate to high confidence (80%), supported by evidence indicating malware embedded in legitimate-looking GTM containers. Under the Collection tactic, the analysis identified Input Capture: Keylogging (T1056.001) with high confidence (90%), supported by evidence indicating capturing payment details (card number, CVV, expiration date) and Automated Collection (T1119) with moderate to high confidence (80%), supported by evidence indicating targets Magento/Adobe Commerce stores to capture payment details. Under the Credential Access tactic, the analysis identified Modify Authentication Process: Multi-Factor Authentication Interception (T1556.003) with moderate to high confidence (70%), supported by evidence indicating steal credit card details from e-commerce checkout pages. Under the Defense Evasion tactic, the analysis identified Obfuscated Files or Information (T1027) with high confidence (90%), supported by evidence indicating stolen data is obfuscated using XOR encryption, Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (80%), supported by evidence indicating abuses Stripe’s API infrastructure (cus_TfFjAAZQNOYENR), and Subvert Trust Controls: SIP and Trust Provider Hijacking (T1553.003) with moderate to high confidence (70%), supported by evidence indicating abuses trusted domains googletagmanager.com and api.stripe.com. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating exfiltrated via Stripe’s API by creating fake customer records and Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.001) with moderate to high confidence (80%), supported by evidence indicating uses Google Firestore to host payload and store stolen data. Under the Impact tactic, the analysis identified Data Destruction (T1485) with moderate to high confidence (70%), supported by evidence indicating malware wipes local traces to avoid detection and Data Manipulation: Stored Data Manipulation (T1565.001) with moderate confidence (60%), supported by evidence indicating creates fake customer records under attacker’s Stripe account. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Stripe Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/stripe/incident/ADOSTRGOO1780611936
- Stripe CyberSecurity Rating page: https://www.rankiteo.com/company/stripe
- Stripe Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/adostrgoo1780611936-google-stripe-magentoadobe-commerce-cyber-attack-december-2025/
- Stripe CyberSecurity Score History: https://www.rankiteo.com/company/stripe/history
- Stripe CyberSecurity Incident Source: https://www.bleepingcomputer.com/news/security/credit-card-theft-campaign-abuses-stripe-to-host-stolen-payment-info/
- 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