Incident Score: Analysis & Impact (CYB1768350463)
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 Cyble's Ransomware 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 Cyble 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 Cyble breach identified under incident ID CYB1768350463.
The analysis begins with a detailed overview of Cyble's information like the linkedin page: https://www.linkedin.com/company/cyble-global, the number of followers: 83862, the industry type: Computer and Network Security and the number of employees: 250 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 735 and after the incident was 625 with a difference of -110 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 Cyble and their customers.
A newly reported cybersecurity incident, "deVixor Android Banking Malware Campaign", has drawn attention.
A new Android banking malware named deVixor can launch ransomware attacks in addition to credential theft and user surveillance.
The disruption is felt across the environment, affecting Android devices, and exposing Banking credentials, OTPs, account balances, card numbers, messages from banks/cryptocurrency exchanges, contacts, keystrokes, screenshots, device notifications, personally identifiable information (PII).
Formal response steps have not been shared publicly yet.
The case underscores how Ongoing, teams are taking away lessons such as Modern Android banking malware has evolved into scalable, service-driven criminal platforms with modular capabilities, persistent configurations, and active development cycles. Traditional detection mechanisms may be evaded due to Telegram-based C&C infrastructure, and recommending next steps like Avoid downloading APK files from untrusted sources, Monitor for phishing campaigns targeting Android users and Enhance detection for Accessibility Service abuse.
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: Spearphishing Link (T1566.001) with high confidence (90%), supported by evidence indicating spreads via phishing websites impersonating automotive businesses and Phishing: Spearphishing Attachment (T1566.002) with high confidence (90%), supported by evidence indicating luring victims into downloading malicious APK files. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: Malicious APK (T1623) with high confidence (90%), with evidence including malicious APK files, and supports nearly 50 commands including ransomware deployment and Obtain Capabilities: Malicious App (T1406) with high confidence (90%), supported by evidence indicating malicious APK files via fake automotive discount websites. Under the Persistence tactic, the analysis identified Event Triggered Execution: Accessibility Features (T1624.001) with high confidence (90%), supported by evidence indicating exploitation of Android’s Accessibility Service and Create or Modify System Process: Windows Service (T1543.003) with moderate to high confidence (70%), supported by evidence indicating storing attack parameters in LockTouch.json to persist across reboots. Under the Privilege Escalation tactic, the analysis identified Event Triggered Execution: Accessibility Features (T1624.001) with high confidence (90%), supported by evidence indicating exploitation of Android’s Accessibility Service. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1622) with moderate to high confidence (80%), supported by evidence indicating google Play Protect bypass techniques, Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (70%), supported by evidence indicating blocking uninstallation, and Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (80%), supported by evidence indicating leverages Firebase for command delivery. Under the Credential Access tactic, the analysis identified Adversary-in-the-Middle: Web Session Cookie (T1557.003) with high confidence (90%), supported by evidence indicating webView-based JavaScript injection for banking credentials, Steal Application Access Token (T1636) with moderate to high confidence (80%), supported by evidence indicating harvests OTPs, banking credentials, and Input Capture: Keylogging (T1056.001) with high confidence (90%), supported by evidence indicating captures keystrokes. Under the Discovery tactic, the analysis identified File and Directory Discovery (T1420) with moderate to high confidence (80%), supported by evidence indicating contacts, device notifications, screenshots and Software Discovery (T1418) with moderate to high confidence (70%), supported by evidence indicating messages from banks/cryptocurrency exchanges. Under the Collection tactic, the analysis identified Screen Capture (T1113) with high confidence (90%), supported by evidence indicating captures screenshots, Input Capture: Keylogging (T1056.001) with high confidence (90%), supported by evidence indicating captures keystrokes, Data from Local System: Email Collections (T1213.003) with moderate to high confidence (70%), supported by evidence indicating messages from banks/cryptocurrency exchanges, and Steal Application Access Token (T1636) with moderate to high confidence (80%), supported by evidence indicating harvests OTPs, account balances, card numbers. Under the Command and Control tactic, the analysis identified Web Service: Bidirectional Communication (T1102.002) with high confidence (90%), supported by evidence indicating leverages Firebase for command delivery and Web Service: Dead Drop Resolver (T1102.001) with moderate to high confidence (80%), supported by evidence indicating telegram-based bot infrastructure for scalable control. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating data exfiltration such as Yes (sent to C&C server) and Exfiltration Over Alternative Protocol: Unencrypted/Obfuscated Non-C2 Protocol (T1048.003) with moderate to high confidence (70%), supported by evidence indicating telegram-based bot infrastructure for scalable control. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with high confidence (90%), supported by evidence indicating locks devices and demands TRON cryptocurrency payments and Endpoint Denial of Service (T1469) with moderate to high confidence (80%), supported by evidence indicating device locking via ransomware. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Cyble Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/cyble-global/incident/CYB1768350463
- Cyble CyberSecurity Rating page: https://www.rankiteo.com/company/cyble-global
- Cyble Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/cyb1768350463-devixor-ransomware-january-2026/
- Cyble CyberSecurity Score History: https://www.rankiteo.com/company/cyble-global/history
- Cyble CyberSecurity Incident Source: https://thecyberexpress.com/android-banking-malware-devixor-ransomware/
- 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