Skip to main content
Mallory
← Back to News
credential-stealer-activityoffensive-tooling-releasecommand-and-control-methoddefense-evasion-method

BankBot Android Banking Trojan Spread via Leaked Code, Google Play, and APK Markets

Malware Intelligence · 3 sources · Updated 3mo ago · First seen Jan 5, 2017

BankBot Android Banking Trojan Spread via Leaked Code, Google Play, and APK Markets

The Android banking trojan BankBot expanded rapidly after the source code for its precursor, BankBotAlpha, and its PHP command-and-control panel were posted on a Russian forum, enabling multiple copycat variants and new campaigns. Researchers found the malware requesting Device Administrator privileges, hiding its launcher icon, intercepting and deleting SMS messages, collecting device identifiers and banking-app data, and sending stolen information to attacker-controlled servers. Early variants focused heavily on Russian and Ukrainian banks and included phishing templates for PrivatBank and Visa QIWI Wallet, while later samples broadened targeting and added stronger evasion and credential-theft capabilities.

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.

7 events · 2016 – Nov 2017
  1. Nov 2017

    Second month of Google Play BankBot dropper activity reported

    ESET said the Google Play BankBot dropper activity continued into November 2017 as part of a second campaign. The second campaign used additional droppers and infrastructure to deliver BankBot samples.

    Malicious apps attempt to distribute malware via Google Play once again
  2. Oct 2017

    BankBot campaigns use Google Play droppers

    ESET reported two Android malware campaigns in October and November 2017 that used apps uploaded to Google Play as droppers for BankBot banking malware. The campaigns relied on malicious or trojanized apps to infect users.

    Malicious apps attempt to distribute malware via Google Play once again
  3. Reported Sep 19, 20179y ago

    New BankBot strains appear in APK markets and Google Play

    New BankBot strains later appeared in third-party APK markets and the official Google Play Store. Fortinet said these newer samples remained very similar to the code leaked in late 2016 while adding broader app injection support and call-blocking logic.

    A Look Into The New Strain Of BankBot
  4. Jan 5, 201710y ago

    BankBotAlpha variants reach VirusTotal

    Variants of BankBotAlpha appeared rapidly after the source leak and had reached VirusTotal by early January 2017. Fortinet later counted 141 variants using the same internal package name.

    BankBot, the Prequel
  5. Dec 26, 201610y ago

    Fortinet detects first BankBotAlpha sample

    Fortinet reported detecting its first BankBotAlpha sample shortly after the forum leak. This marked the malware's appearance in the wild beyond the original posting.

    BankBot, the Prequel
  6. Dec 19, 201610y ago

    BankBotAlpha advertised on Russian forum

    A user named "maza-in" advertised the BankBotAlpha Android banking malware project on a Russian forum and presented it as a tutorial for building an Android banker. The post made the source code and PHP command-and-control panel publicly available.

    BankBot, the Prequel
  7. 2016

    BankBot surfaces in the second half of 2016

    Fortinet described BankBot as an Android banking trojan family that first surfaced in the second half of 2016. Its purpose was to steal banking credentials from Android users.

    A Look Into The New Strain Of BankBot
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 →

Malware

2 linked

Affected products

1 linked
Android

Organizations

2 linked
QiwiPrivatBank

Observables

244 linked

Indicator values are masked on this page. View all 244 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.