Threat ResearchAndroid banking trojanMarch 2022 (public disclosure; Group-IB traces related activity to June 2021)Analyzed 2026-09-08

Godfather: recovered C2 indicators & analysis

Godfather is an Android banking trojan, derived from the leaked Anubis source code and sold as malware-as-a-service, that steals credentials and commits on-device fraud against a very large global list of banking and cryptocurrency apps. · also known as GodFather

What Godfather is

Godfather (also stylized "GodFather") is an Android banking trojan first disclosed publicly by ThreatFabric in March 2022, with related activity traced back by Group-IB to June 2021. Group-IB's analysis identified it as a successor built on the source code of the Anubis banking trojan, whose code leaked on an underground forum in January 2019; the two share command-and-control command handling and web-fake (overlay) modules, though Godfather was modernized for newer Android versions and dropped some legacy Anubis features such as audio recording and location tracking. Godfather is distributed under a malware-as-a-service model to multiple operators, so the exact configuration and target set vary between campaigns.

In its established form, Godfather relies on Android's Accessibility Service to drive the infection: it logs keystrokes, captures screen content, and can perform automated on-screen actions. It presents HTML overlay screens ("web fakes") on top of, or in place of, targeted banking and cryptocurrency apps to harvest login credentials, and it intercepts SMS and push notifications to defeat one-time-password and two-factor authentication. Reported capabilities also include screen recording (the screen is recorded and the resulting file exfiltrated), call-log harvesting, a VNC-style remote-control module implemented with native libraries, and a SOCKS5 proxy for tunneling traffic through the infected device.

Later variants moved substantial logic into native code to reduce detection and, by 2024-2025, adopted an on-device app-virtualization technique. Documented by Cyble (November 2024) and analyzed in depth by Zimperium zLabs (June 2025), this approach embeds an open-source virtualization framework (such as VirtualApp) together with Xposed-style hooking inside the malicious host app. Instead of only drawing a fake overlay, the malware intercepts the launch intent for a targeted app via its accessibility permission, redirects the user to a copy of the real banking or crypto app running inside its controlled sandbox, and hooks the app's internals (for example the OkHttp client) to read credentials, PINs, tap events, and backend responses in real time while showing decoy screens. This provides a near-seamless experience and enables full account-takeover actions from inside the genuine app.

Godfather retrieves its command-and-control address using a dead-drop resolver: earlier samples decrypted the description of an actor-controlled Telegram channel (Blowfish-encoded), while later samples fetch a Base64-encoded C2 URL from a Telegram profile before communicating with the resolved server over HTTP(S); WebSocket connections have also been reported. Its target list has grown over time, from more than 400 banking and cryptocurrency apps across 16 countries reported by Group-IB in 2022 to roughly 484-500 banking, cryptocurrency, and e-commerce apps in 2024-2025 reporting, with observed geographic expansion into countries including Japan, Singapore, Greece, and Azerbaijan. The virtualization campaign analyzed by Zimperium was tightly focused on about a dozen Turkish financial institutions. Consistent with a Russian-speaking operator base, the malware halts execution when the device language is one of several CIS-region locales (RU, AZ, AM, BY, KZ, KG, MD, UZ, TJ).

Capabilities

Known C2 / channel types: HTTP(S), Telegram (dead-drop for C2 address via channel description / profile), WebSocket.

MITRE ATT&CK (Mobile)

Techniques commonly associated with Godfather:

IDTechnique
T1417Input Capture
T1516Input Injection
T1582SMS Control
T1517Access Notifications
T1636Protected User Data
T1513Screen Capture
T1437Application Layer Protocol
T1655Masquerading

What Privara Unmask recovered

Both samples used a Telegram channel as a dead-drop for their live C2 address. The channel URLs were recovered; the transport IP 149.154.167.99:443 is Telegram infrastructure, not a distinct C2, and is deliberately not listed as an indicator. The analysis ran on a de-emulated Android 17 device that the sample could not fingerprint as virtual, so it behaved as it would on a real handset.

Package com.motivities.grubroot
SHA-256 a6ed100ae42e4fdabfd1b4c992762152bc4a11cc8e521b647b444c75bb7a9782
Source MalwareBazaar (abuse.ch)

Package com.parcellize.unmatrimonial
SHA-256 c2bccfc8b3bdf2da5fb5c22055a9c4859256be7904933e9e0b92fa31fd0420d3
Source MalwareBazaar (abuse.ch)
Community contribution. Contributed to ThreatFox as net-new intelligence on 2026-09-08 — both Telegram dead-drop channel URLs (TAJ APPS account).

Indicators of compromise (IOCs)

IndicatorTypeRoleConfidenceStatus
t.me/yazmozaramekos
Telegram dead-drop channel (from run 189)
urlC2highoffline
t.me/paperokomozase
Telegram dead-drop channel (from run 190)
urlC2highoffline
Status note. The indicators above were unresponsive (offline / sinkholed) at analysis time and are published as historical threat intelligence. Co-observed benign and environmental artifacts have been removed rather than reported as C2.

External references

Methodology & honest limits

This sample was obtained from MalwareBazaar and detonated in a controlled, isolated environment. C2 identity was recovered from the executing sample and its configuration. We report only what the analysis established: an offline sample yields a C2 identity, not a live beacon, and we say so. Nothing here is inferred beyond the evidence.

Analyze your own Android samples like this

Privara Unmask detonates arm64 samples on a de-emulated Android 17 device that anti-analysis code can't fingerprint — recovering C2, config and IOCs automatically, with a clean rollback per sample.

See the sandbox → Request a demo