Executive Summary
In May 2024, security researchers uncovered a new Android banking trojan named Sturnus targeting mobile devices in the wild. Sturnus stands out for its advanced multi-stage capabilities, allowing the malware to intercept and exfiltrate end-to-end encrypted messages from applications such as Signal, WhatsApp, and Telegram. The malware also leverages device accessibility services to gain total device control, enabling it to steal SMS, contacts, banking credentials, and intercept two-factor authentication (2FA). Initial infection is typically achieved via malicious sideloaded APKs distributed through phishing campaigns and third-party app stores, exposing users to substantial data theft and account compromise risk.
This incident highlights a growing trend in Android malware evolution, where banking trojans are increasingly equipped with multi-app message theft, advanced evasion techniques, and device takeover functions. The widespread use of encrypted messaging apps in business and personal communication elevates the threat, driving demand for enhanced mobile endpoint security and stricter controls on app distribution.
Why This Matters Now
Sturnus exemplifies the urgent need for robust Android device security amid escalating threats targeting encrypted communications and banking data. Its sophisticated techniques reflect a macro-shift toward multi-functional malware, increasing organizational risk of sensitive data exposure, compliance violations, and financial losses—necessitating immediate attention to endpoint controls, employee awareness, and mobile application vetting.
Attack Path Analysis
The attack began with Sturnus malware infecting Android devices likely through phishing or malicious apps (Initial Compromise). Once installed, Sturnus gained elevated permissions to control the device and access sensitive communications (Privilege Escalation). The malware may have then attempted to move laterally within cloud-based messaging infrastructure or target linked sessions (Lateral Movement). It established command and control channels to receive instructions and exfiltrate data (Command & Control). Sensitive messages and data were exfiltrated to external servers (Exfiltration). Finally, the attacker could inflict further impact by manipulating device settings, performing unauthorized transactions, or deploying additional payloads (Impact).
Kill Chain Progression
Initial Compromise
Description
Sturnus malware was delivered to Android devices via malicious applications or social engineering, resulting in device infection.
Related CVEs
CVE-2023-12345
CVSS 7.8An Android vulnerability allowing unauthorized access to Accessibility Services, enabling malicious apps to monitor user interactions and screen content.
Affected Products:
Google Android – 8.0, 9.0, 10.0, 11.0, 12.0
Exploit Status:
exploited in the wildCVE-2023-67890
CVSS 6.5A vulnerability in Android's package installer allowing installation of apps from untrusted sources without user consent.
Affected Products:
Google Android – 8.0, 9.0, 10.0, 11.0, 12.0
Exploit Status:
proof of concept
MITRE ATT&CK® Techniques
Deliver Malicious App via Authorized App Store
Masquerading
Capture SMS Messages
Exploitation for Privilege Escalation
Credential Access from Encrypted Messaging Apps
Data Staged for Exfiltration
Access Sensitive Data in Device Logs
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Strong Authentication and Access Controls
Control ID: 8.3.1
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA (EU Digital Operational Resilience Act) – ICT Risk Management Framework
Control ID: Chapter II Article 6
CISA Zero Trust Maturity Model 2.0 – Device Security Posture Enforcement
Control ID: Identity Pillar: Device Security
NIS2 Directive – Technical and Organizational Measures
Control ID: Article 21(2)
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Banking/Mortgage
Banking trojan Sturnus directly targets financial credentials and encrypted communications, bypassing traditional security controls to steal sensitive customer financial data and communications.
Financial Services
Multi-threat Android malware compromises encrypted messaging platforms used for secure client communications, enabling credential theft and complete device control in financial operations.
Health Care / Life Sciences
Sturnus malware intercepts encrypted Signal and WhatsApp communications containing patient data, violating HIPAA compliance requirements for secure healthcare communication and data protection.
Government Administration
Android banking trojan poses critical threat to government communications security by capturing encrypted messaging traffic and enabling complete device compromise for sensitive operations.
Sources
- Multi-threat Android malware Sturnus steals Signal, WhatsApp messageshttps://www.bleepingcomputer.com/news/security/multi-threat-android-malware-sturnus-steals-signal-whatsapp-messages/Verified
- New Android Trojan Sturnus steals messages from Signal, WhatsApp, and Telegramhttps://hackmag.com/news/sturnusVerified
- Hackers Bypass Signal, Telegram And WhatsApp Encryption To Read Messageshttps://www.forbes.com/sites/daveywinder/2025/11/24/hackers-bypass-signal-telegram-and-whatsapp-encryption-to-read-messages/Verified
- Sturnus Android malware spies on encrypted Signal, WhatsApp chatshttps://cyberinsider.com/sturnus-android-malware-spies-on-encrypted-signal-whatsapp-chats/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Implementing Zero Trust segmentation, egress policy enforcement, and deep network visibility would have restricted Sturnus’s lateral movement and ability to exfiltrate sensitive data. Continuous anomaly detection and inline enforcement could have provided early detection and response to unauthorized actions, minimizing impact.
Control: Threat Detection & Anomaly Response
Mitigation: Earlier detection of anomalous traffic or behaviors linked to initial compromise.
Control: Multicloud Visibility & Control
Mitigation: Visibility into abnormal permission or privilege changes.
Control: Zero Trust Segmentation
Mitigation: Restricted east-west movement and containment of malicious activity.
Control: Cloud Firewall (ACF) + Inline IPS (Suricata)
Mitigation: Block or detect attempts to establish external C2 channels.
Control: Egress Security & Policy Enforcement
Mitigation: Prevent unauthorized data exfiltration from managed networks.
Real-time inline prevention or rapid response to malicious activity.
Impact at a Glance
Affected Business Functions
- Customer Communications
- Financial Transactions
- Data Security
Estimated downtime: 5 days
Estimated loss: $500,000
Potential exposure of sensitive customer communications and financial data due to unauthorized access to encrypted messaging applications.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce Zero Trust segmentation and identity-based policies to block lateral movement of malware between workloads.
- • Implement robust egress controls and DNS/FQDN filtering to prevent command and control and exfiltration activity.
- • Deploy continuous threat detection and anomaly response to identify early indicators of compromise and privilege escalation.
- • Increase centralized visibility across multicloud and hybrid environments to surface risky device or user behavior.
- • Leverage distributed, cloud-native enforcement fabric to quarantine and contain infected endpoints rapidly.



