Skip to main content
Mallory
← Back to News
credential-stealer-activitybotnet-infrastructureoffensive-tooling-releasefinancial-sector-threat

Leaked Android Banking Trojan Code Fueled New Botnet Campaigns

Malware Intelligence · 3 sources · Updated 3mo ago · First seen Feb 20, 2017

Leaked Android Banking Trojan Code Fueled New Botnet Campaigns

Security researchers reported that leaked source code for the Android banking malware GM Bot enabled broader criminal reuse of a trojan capable of stealing banking credentials, intercepting SMS messages, and bypassing two-factor authentication. IBM said the malware—also tracked under names including Slempo, Bankosy, Acecard, and MazarBot—abused Android activity hijacking on older devices to display fake login overlays on legitimate banking apps, making the leak significant because it lowered the barrier for other actors to build or modify mobile banking trojans.

ESET later linked publicly released Android banker and command-and-control source code from a Russian forum to an active banking botnet campaign distributed through trojanized weather apps on Google Play. The newer malware, detected as Trojan.Android/Spy.Banker.HW, posed as World Weather, expanded targeting from 22 Turkish banks to 69 banking apps across Turkey, the UK, Germany, and Austria, and added stronger obfuscation while retaining SMS interception and remote lock and unlock functions. An exposed control panel showed more than 2,800 infected devices, and the hosting provider removed the C2 server after notification.

Hunt this familyPull IOCs and campaign context straight into your stack.
Get the IOCs
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

9 events · 2014 – Feb 20, 2017
  1. Reported Feb 23, 201710y ago

    Hosting provider took down the malware C2 server

    After ESET notified the hosting company, the provider took down the malware's command-and-control server. ESET had previously accessed the exposed panel and observed data from more than 2,800 infected bots.

    Released Android malware source code used to run a banking botnet
  2. Feb 20, 201710y ago

    Google Play removed the malicious World Weather app

    The Trojan.Android/Spy.Banker.HW sample remained on Google Play until February 20, 2017, when it was removed after ESET reported it. The app retained legitimate weather functionality while adding credential theft, SMS interception, and remote lock/unlock features.

    Released Android malware source code used to run a banking botnet
  3. Feb 14, 201710y ago

    Trojanized World Weather app appeared on Google Play

    ESET discovered a newer Android banking trojan variant masquerading as the legitimate app World Weather on Google Play. The sample, detected as Trojan.Android/Spy.Banker.HW, expanded targeting to 69 banking apps across Turkey, the UK, Germany, and Austria.

    Released Android malware source code used to run a banking botnet
  4. Feb 2, 201710y ago

    Botnet C2 server became active

    ESET found that the malware's command-and-control server had been active since February 2, 2017. The exposed control panel was accessible without credentials and provided visibility into more than 2,800 infected devices.

    Released Android malware source code used to run a banking botnet
  5. Dec 26, 201610y ago

    Dr.Web analyzed an earlier Android/Spy.Banker.HH variant

    ESET said Dr.Web had analyzed an earlier malware variant that ESET detected as Android/Spy.Banker.HH starting on December 26, 2016. ESET noted that this sample belonged to the same malware family but was not directly tied to the later Google Play variants.

    Released Android malware source code used to run a banking botnet
  6. Dec 19, 201610y ago

    Android banker source code and C2 panel were posted publicly

    ESET reported that Android banking malware source code and accompanying C&C server code, including a web control panel, had been publicly available on a Russian forum since December 19, 2016. ESET concluded later Google Play banking trojans were built from this released code.

    Released Android malware source code used to run a banking botnet
  7. Reported Feb 21, 201611y ago

    GM Bot operators began selling a second version after the leak

    After the source code leak, IBM said the malware's creators appear to have developed and sold a second GM Bot version on underground forums focused on financial fraud. This indicated continued commercialization of the malware family despite the leak.

    Source code for powerful Android banking malware is leaked | PCWorld
  8. Reported Feb 21, 201611y ago

    GM Bot source code was leaked on an underground forum

    IBM Trusteer analyst Limor Kessem wrote that a buyer of the GM Bot code apparently reposted an encrypted archive containing the malware source code on a forum in December. The password was then shared beyond the original audience, widening distribution of the code.

    Source code for powerful Android banking malware is leaked | PCWorld
  9. 2014

    GM Bot emerged on Russian-speaking underground forums

    IBM said the Android banking malware GM Bot first appeared on Russian-speaking forums in late 2014. The malware was designed to steal banking credentials and SMS-based authentication codes from Android devices.

    Source code for powerful Android banking malware is leaked | PCWorld
Linked entities

Related entities

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.

Open in app →

Organizations

47 linked
DanskebankNatWest GroupIsbankAkbankCommerzbankHSBC HoldingsBawag GroupBarclaysLloyds Banking GroupCapital One Financial Corporation+37 more

Observables

15 linked

Indicator values are masked on this page. View all 15 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?Pull the IOCs, campaigns, and victimology behind this family, ready to push into your SIEM and EDR.
Hunt This Malware
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.