Threat ResearchAndroid banking trojanSeptember 2019Analyzed 2026-09-08

TrickMo: recovered C2 indicators & analysis

TrickMo is an Android banking trojan linked to the TrickBot cybercrime gang that abuses Android accessibility services to intercept one-time passwords, record and stream the screen, phish credentials with overlays, and steal device unlock PINs and patterns for on-device fraud. · also known as Android TrickMo

What TrickMo is

TrickMo is an Android banking trojan first observed in the wild in September 2019 (initially flagged by CERT-Bund) and publicly documented by IBM X-Force in 2020. It is attributed to the operators of the TrickBot Windows banking malware, and its original purpose was to defeat mobile transaction authorization: it intercepted one-time passwords (OTPs) and other SMS/push-based two-factor authentication codes so the gang could authorize fraudulent transfers. The family has continued to evolve well beyond that original OTP-stealer role.

Modern TrickMo variants center on Android accessibility service abuse. Once the accessibility permission is granted, the malware auto-approves further permission prompts, automatically taps through dialogs, dismisses the keyguard, and can obstruct uninstallation. Core capabilities include HTML/WebView overlay attacks that mimic legitimate banking, cryptocurrency, and authenticator apps to phish credentials; keylogging; screen recording and live screen streaming; SMS interception and silent suppression of OTP notifications; broad data exfiltration (SMS, photos, and stored credentials); and remote device control amounting to device takeover. A distinctive later feature is a full-screen fake device-unlock screen (an HTML page) that captures the victim's PIN or unlock pattern and sends it, together with the Android ID, to attacker infrastructure.

In 2024 Cleafy and Zimperium published overlapping research on the family. Cleafy documented a variant delivered by a dropper disguised as Google Chrome that used anti-analysis techniques such as malformed ZIP archives and JSONPacker to conceal its DEX payload, and found a misconfigured command-and-control server exposing roughly 12 GB of exfiltrated victim data (credentials, images, and logs) without authentication. Zimperium's follow-on analysis identified around 40 TrickMo variants, 16 droppers, and 22 command-and-control servers, and estimated at least 13,000 victims, concentrated in Canada, the United Arab Emirates, Turkey, and Germany. C2 communication in these variants used HTTP POST requests carrying JSON payloads.

A 2026 variant reported by ThreatFabric shows further development: it is described as device-takeover malware whose command-and-control traffic was moved off the conventional internet onto The Open Network (TON), using .adnl endpoints routed through an embedded local TON proxy to resist DNS-based takedown. That variant also embeds a SOCKS5 proxy and SSH tunneling, letting an infected device act as a network exit node, and was observed in campaigns in France, Italy, and Austria.

Capabilities

Known C2 / channel types: HTTP(S) REST (JSON over HTTP POST), TON (The Open Network) / ADNL endpoints via embedded local proxy (2026 variant).

MITRE ATT&CK (Mobile)

Techniques commonly associated with TrickMo:

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

What Privara Unmask recovered

C2 recovered from the executed sample. Benign co-observed hosts (an IP-echo service, an attribution SDK endpoint, and a GitHub badge CDN) were classified as noise and excluded. 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 net.dress.absorb
SHA-256 4284e6bbc2fc274d8b0a1f37f91408efc0404e4cae0ba28abc4d583bc59af6bd
Source MalwareBazaar (abuse.ch)
Community contribution. Contributed to ThreatFox as net-new intelligence on 2026-09-08 (TAJ APPS account).

Indicators of compromise (IOCs)

IndicatorTypeRoleConfidenceStatus
btceducationcenter.comdomainC2highoffline
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