Threat ResearchAndroid banking trojan / RAT (device-takeover)January 2023Analyzed 2026-09-14

Hook: recovered C2 indicators & analysis

Hook is an Android banking trojan and remote-access tool, derived from the ERMAC codebase and sold as malware-as-a-service, that combines overlay credential theft with real-time device takeover through VNC-style remote control abusing the accessibility service. · also known as HookBot

What Hook is

Hook is an Android banking trojan with remote-access-tool (RAT) capabilities that was first publicly reported in January 2023. It was advertised on a Russian-language underground forum by the actor known as DukeEugene, who was also associated with the earlier ERMAC and BlackRock families. Although Hook's author claimed it was written from scratch, ThreatFabric's analysis found that the majority of its code base is derived from ERMAC, including reused code and Russian-language comments; Hook is therefore generally assessed as an ERMAC fork or successor rather than a wholly new family. It was offered as malware-as-a-service on a subscription basis.

Hook inherits ERMAC's core banking-trojan functionality and extends it. It performs overlay (web-inject) attacks against a large set of banking and cryptocurrency applications to harvest credentials, logs keystrokes, intercepts and sends SMS messages, and monitors the clipboard (including substituting attacker-controlled cryptocurrency wallet addresses). It abuses Android accessibility services to read on-screen content and inject input. Its headline addition over ERMAC is a VNC-style remote-control / device-takeover (DTO) capability: operators can stream the victim's screen and drive the UI in real time via accessibility-driven gestures (taps and swipes), enabling a complete on-device fraud chain without an out-of-band channel. Reported capabilities also include taking photos with the front-facing camera, file-manager access to list and exfiltrate files, harvesting Google session cookies, geolocation retrieval, and interaction with messaging apps such as WhatsApp.

The original Hook project was reportedly shut down in April 2023 when DukeEugene announced they were stepping away; support was said to continue under an actor named RedDragon, and the source code was reportedly offered for sale on an underground forum in May 2023. In August 2025, Zimperium's zLabs documented a substantially expanded variant tracked as Hook version 3, which they reported supports 107 remote commands (38 of them new). This variant adds a full-screen ransomware-style extortion overlay (triggered by a 'ransome' command and dismissed with 'delete_ransome') that displays a wallet address and amount fetched from the command-and-control server, along with fake NFC-capture overlays ('takenfc'), fraudulent card-entry and lock-screen overlays for capturing card data, PINs and unlock patterns, and transparent gesture-recording overlays. Zimperium also observed Hook samples being distributed via phishing sites and public GitHub repositories, in some cases alongside other families such as ERMAC and Brokewell.

For command-and-control, Hook communicates with attacker infrastructure over HTTP and added WebSocket-based communication (using the Socket.IO protocol) for real-time command delivery. Command payloads have been reported as encrypted with AES-256-CBC using a hardcoded key and then Base64-encoded. Targeting reported for early versions spanned banking apps across multiple countries including the United States, Spain, Australia, Poland, Canada, Turkey, the United Kingdom, France, Italy and Portugal, with the overlay target list numbering in the hundreds of applications.

Capabilities

Known C2 / channel types: HTTP(S), WebSocket (Socket.IO).

MITRE ATT&CK (Mobile)

Techniques commonly associated with Hook:

IDTechnique
T1417Input Capture
T1516Input Injection
T1582SMS Control
T1636Protected User Data
T1437Application Layer Protocol
T1414Clipboard Data
T1513Screen Capture
T1512Video Capture
T1418Software Discovery
T1406Obfuscated Files or Information

What Privara Unmask recovered

Recovered from the executed sample during automated detonation on a de-emulated Android 17 device. The 2026-09-08 sample yielded its C2 host from recovered runtime configuration. A second sample (2026-09-14) was observed connecting to two high ports on a single host by the platform's kernel tracer — a kprobe on security_socket_connect, below the application, so the endpoints are observed rather than inferred from strings. 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.half.powder
SHA-256 6ca691c97ab0028ce9acade5d079289668b1d0339ad330181c84fc7e7114c509
Source MalwareBazaar (abuse.ch)

Package p31e2586d.p0e6e1473.pca88ca83
SHA-256 2b332adf4e52168cbd2e76866165a5c6f421d15b5778d44f78f0d86c4c26b9fa
Source MalwareBazaar (abuse.ch)
Community contribution. Independently corroborated an existing ThreatFox entry (submitted 2026-09-08, TAJ APPS account).

Indicators of compromise (IOCs)

IndicatorTypeRoleConfidenceStatus
hrjob-forward-build.storedomainC2highoffline
23.254.229.105:13500
observed by kernel tracer (kprobe on security_socket_connect) — the sample's own process called connect() to this endpoint
ip:portC2highunresponsive
23.254.229.105:8055
observed by kernel tracer (kprobe on security_socket_connect) — the sample's own process called connect() to this endpoint
ip:portC2highunresponsive

Recovered but withheld from the feed (precision over volume):

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