Incident Score: Analysis & Impact (JPMPAY1777400719)
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 JPMorganChase'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 JPMorganChase 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 JPMorganChase breach identified under incident ID JPMPAY1777400719.
The analysis begins with a detailed overview of JPMorganChase's information like the linkedin page: https://www.linkedin.com/company/jpmorganchase, the number of followers: 7067454, the industry type: Financial Services and the number of employees: 224255 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 817 and after the incident was 810 with a difference of -7 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 JPMorganChase and their customers.
Chase recently reported "BlobPhish: A Stealthy, Memory-Resident Phishing Campaign Targeting Microsoft 365 and Financial Institutions", a noteworthy cybersecurity incident.
Since October 2024, a sophisticated phishing campaign dubbed *BlobPhish* has been silently harvesting credentials from Microsoft 365 users and major U.S.
The disruption is felt across the environment, affecting Microsoft 365, Banking portals (Chase, Capital One, PayPal) and OneDrive, and exposing Credentials (Microsoft 365, banking portals), personally identifiable information (PII).
Formal response steps have not been shared publicly yet.
Overall, the incident is a reminder of why proactive monitoring and strong governance matter.
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 Phishing (T1566) with high confidence (95%), supported by evidence indicating phishing emails mimicking financial alerts, invoices, or document shares, Phishing: Spearphishing Attachment (T1566.001) with high confidence (90%), supported by evidence indicating pDF attachments with QR codes, and Phishing: Spearphishing Link (T1566.002) with high confidence (90%), supported by evidence indicating shortened URLs (e.g., t.co) redirecting to attacker-controlled HTML page. Under the Execution tactic, the analysis identified JavaScript (T1059.007) with high confidence (90%), supported by evidence indicating javaScript loader decodes bundled phishing payload in browser memory and User Execution: Malicious Link (T1204.001) with moderate to high confidence (85%), supported by evidence indicating victims click phishing links in emails or PDF attachments. Under the Credential Access tactic, the analysis identified Input Capture: Keylogging (T1056.001) with high confidence (90%), supported by evidence indicating phishing page impersonates Microsoft 365, OneDrive, or banking portals and Adversary-in-the-Middle: LLMNR/NBT-NS Poisoning and SMB Relay (T1557.003) with lower confidence (30%), supported by evidence indicating blob URL deception may facilitate AiTM techniques (implied). Under the Defense Evasion tactic, the analysis identified Obfuscated Files or Information (T1027) with high confidence (90%), supported by evidence indicating javaScript loader decodes bundled phishing payload in memory, Indicator Removal: File Deletion (T1070.004) with high confidence (95%), supported by evidence indicating blob URL revoked immediately after use, leaving no disk artifacts, and Hide Artifacts: Hidden Window (T1564.003) with moderate to high confidence (80%), supported by evidence indicating phishing page generated in browser memory, no standalone HTTP response. Under the Collection tactic, the analysis identified Input Capture: Keylogging (T1056.001) with high confidence (90%), supported by evidence indicating failed-login counter ensures multiple credential entries and Automated Collection (T1119) with moderate to high confidence (80%), supported by evidence indicating stolen data exfiltrated via HTTP POST to compromised WordPress sites. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating stolen data exfiltrated via HTTP POST to compromised WordPress sites and Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with moderate confidence (50%), supported by evidence indicating compromised WordPress sites used as exfiltration endpoints. Under the Impact tactic, the analysis identified Account Access Removal (T1531) with moderate to high confidence (70%), supported by evidence indicating business email compromise (BEC), Microsoft 365 tenant takeovers and Data Encrypted for Impact (T1486) with moderate confidence (60%), supported by evidence indicating potential ransomware deployment mentioned. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- JPMorganChase Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/jpmorganchase/incident/JPMPAY1777400719
- JPMorganChase CyberSecurity Rating page: https://www.rankiteo.com/company/jpmorganchase
- JPMorganChase Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/jpmpay1777400719-paypal-chase-cyber-attack-october-2024/
- JPMorganChase CyberSecurity Score History: https://www.rankiteo.com/company/jpmorganchase/history
- JPMorganChase CyberSecurity Incident Source: https://cybersecuritynews.com/blobphish-phishing-attack/
- 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