Incident Score: Analysis & Impact (MEX1787049361)
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 MEXC.com'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 MEXC.com 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 MEXC.com breach identified under incident ID MEX1787049361.
The analysis begins with a detailed overview of MEXC.com's information like the linkedin page: https://www.linkedin.com/company/mexc-com, the number of followers: 0, the industry type: Technology, Information and Internet and the number of employees: 19 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 821 and after the incident was 796 with a difference of -25 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 MEXC.com and their customers.
On 01 June 2026, a cybersecurity incident called "New Android Malware-as-a-Service Platform 'Octagon' Targets Banking and Crypto Users" came to light.
A previously undocumented Android malware platform, Octagon, has emerged as a sophisticated malware-as-a-service (MaaS) offering from a Russian-speaking threat actor operating under the handle AndroidKitKat.
The disruption is felt across the environment, affecting Android devices, and exposing Seed phrases, Passwords and PINs.
Formal response steps have not been shared publicly yet.
The case underscores how Ongoing, teams are taking away lessons such as Octagon's abuse of Android Accessibility Services and manual permission grants makes it difficult for traditional security measures like Google Play Protect to detect. Users should avoid sideloading apps and scrutinize accessibility service requests, and recommending next steps like Monitor for sideloaded apps requesting accessibility access alongside SMS permissions, Detect encrypted outbound TCP traffic on port 4444 with Octagon’s shared client strings and Watch for unusual battery-optimization exclusions or foreground service execution.
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 Deliver Malicious App via Other Means (T1476) with high confidence (90%), supported by evidence indicating spreads via sideloaded APKs disguised as legitimate apps and Phishing: Spearphishing Attachment (T1566.001) with moderate to high confidence (80%), supported by evidence indicating fake Play Store pages and government branding to trick victims. Under the Execution tactic, the analysis identified Abuse Accessibility Features (T1629) with high confidence (95%), supported by evidence indicating tricks victims into enabling Android Accessibility Services and Obtain Device Access (T1406) with high confidence (90%), supported by evidence indicating hidden VNC-style remote control enables screen interaction. Under the Persistence tactic, the analysis identified Event Triggered Execution: Boot or Logon Initialization Scripts (T1628) with moderate to high confidence (80%), supported by evidence indicating boot execution and foreground services ensure malware remains active and Hijack Execution Flow: Path Interception by Unquoted Path (T1627) with moderate to high confidence (70%), supported by evidence indicating isolated processes and battery-optimization bypasses. Under the Privilege Escalation tactic, the analysis identified Abuse Accessibility Features (T1629) with high confidence (90%), supported by evidence indicating accessibility Services allow interface manipulation and system actions. Under the Defense Evasion tactic, the analysis identified Indicator Removal (T1622) with moderate to high confidence (80%), supported by evidence indicating modular design allows rapid C2 infrastructure changes and Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (70%), supported by evidence indicating battery-optimization bypasses evade Android power-saving features. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1630) with high confidence (90%), supported by evidence indicating phishing overlays steal seed phrases, passwords, and PINs, Steal or Forge Authentication Certificates (T1626) with moderate to high confidence (80%), supported by evidence indicating captures unlock patterns via Android System UI and lock screens, and Modify Authentication Process: Multi-Factor Authentication Interception (T1556.003) with high confidence (90%), supported by evidence indicating intercepts SMS messages to bypass 2FA. Under the Discovery tactic, the analysis identified File and Directory Discovery (T1420) with moderate to high confidence (80%), supported by evidence indicating grants visibility into installed apps and screen content and Software Discovery (T1418) with moderate to high confidence (80%), supported by evidence indicating inspects installed apps and accessibility-node data. Under the Collection tactic, the analysis identified Input Capture: Keylogging (T1412) with high confidence (90%), supported by evidence indicating captures unlock patterns and inputs via accessibility abuse, Screen Capture (T1636) with moderate to high confidence (80%), supported by evidence indicating hidden VNC-style remote control enables screenshots, and Clipboard Data (T1637) with moderate to high confidence (70%), supported by evidence indicating likely captures clipboard data via accessibility features. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with high confidence (90%), supported by evidence indicating communicates over TCP port 4444 with AES-GCM encryption and Ingress Tool Transfer (T1105) with moderate to high confidence (70%), supported by evidence indicating multi-stage APK chain observed in campaigns. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating data exfiltration via OctagonBridge and C2 panel and Exfiltration Over Alternative Protocol: Exfiltration Over Symmetric Encrypted Non-C2 Protocol (T1048.001) with moderate to high confidence (80%), supported by evidence indicating aES-GCM encrypted traffic on port 4444. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with moderate confidence (50%), supported by evidence indicating c2 traffic uses AES-GCM encryption (not ransomware) and Financial Theft (T1657) with high confidence (90%), supported by evidence indicating enables cryptocurrency theft and account takeovers. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- MEXC.com Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/mexc-com/incident/MEX1787049361
- MEXC.com CyberSecurity Rating page: https://www.rankiteo.com/company/mexc-com
- MEXC.com Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/mex1787049361-mexc-cyber-attack-june-2026/
- MEXC.com CyberSecurity Score History: https://www.rankiteo.com/company/mexc-com/history
- MEXC.com CyberSecurity Incident Source: https://gbhackers.com/octagon-android-bot/
- 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