Researchers detailed the discovery of Geost, a previously unknown Android banking botnet that targeted users in Russia and harvested SMS messages, banking data, and other sensitive information from infected devices. Analysis indicated the operation relied on at least 13 command-and-control servers, more than 140 domains, and over 150 Android APKs, with one observed server alone suggesting a conservative victim count of roughly 871,200 devices. The malware monitored account balances and appeared to target several major Russian banks and payment services, placing it among the more significant mobile banking threats documented in the region.
The botnet was uncovered after multiple operational security mistakes by its operators exposed internal activity and infrastructure. Investigators found Geost administrators using the HtBot illegal proxy network, sending unencrypted C2 traffic, reusing infrastructure, and maintaining poorly secured developer communications that leaked credentials and Skype chat logs. Those errors allowed researchers to map relationships between aliases, infrastructure, and probable members of the underground group behind the malware, while broader reporting on Android banking malware such as Asacub underscored the continuing rise of mobile banker campaigns aimed at financial theft.

Pull IOCs and campaign context straight into your stack.
4 events from the most recent confirmed update back to the earliest known activity.
Trend Micro released a detailed reverse-engineering analysis of Geost, describing its distribution via unofficial websites, multi-stage architecture, obfuscation, persistence mechanisms, and command-and-control features. The report also documented capabilities including SMS interception, theft of contacts and call logs, remote device locking, and other operator commands, and provided indicators of compromise.
Researchers obtained a leaked Skype chat log tied to people related to the Geost operation, containing unencrypted credentials, links, wallet identifiers, and other sensitive data. The log spanned more than 6,200 lines over eight months and helped reveal internal relationships and probable members connected to the botnet.
The investigation found that Geost used at least 13 command-and-control servers, more than 140 malicious domains, and over 150 Android APK samples. Based on one observed server showing about 72,600 victims, the researchers conservatively estimated roughly 871,200 victims across the botnet's infrastructure.
Researchers identified Geost as a previously unknown Android banking botnet targeting Russian users after analyzing traffic that passed through a monitored HtBot malware proxy node used by the botmasters. The discovery was enabled by multiple operational security failures, including unencrypted command-and-control traffic.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. View all 113 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Pull the IOCs, campaigns, and victimology behind this family, ready to push into your SIEM and EDR.
3 references tracked. Mallory keeps watching after this page renders.
trendmicro.com
Open sourcevirusbulletin.com
Open sourcesecurelist.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.