RedHook Android Trojan Automatically Enables Wireless ADB Debugging to Hijack Devices Without Root or User Interaction
The RedHook trojan, first described in July 2025, has received an unprecedented update that lets it independently enable wireless ADB debugging on compromised Android smartphones, achieving system-shell privileges without root or any action from the victim.
According to researchers at Group-IB, the infection follows a familiar social-engineering pattern. Attackers contact targets by phone or messenger, posing as bank or government representatives, and persuade them to download an application from a fake website styled to resemble an official app store. The malicious APK files themselves are hosted on legitimate infrastructure—GitHub repositories and Amazon S3 cloud storage—reducing the likelihood of detection by security solutions.
After installation, victims are convinced to grant the app accessibility-service permissions under the pretext of enabling full functionality. This single permission serves as the gateway to everything else. With accessibility access, RedHook automatically opens the device settings, taps the build number seven times to reveal the developer menu, and activates wireless debugging—all hidden behind a full-screen overlay.
The malware then runs its own ADB client, which connects directly to the phone’s local debugging server using the loopback address, eliminating any need for an external computer. The technique is built on code from the popular Shizuku framework that advanced users normally employ to extend app capabilities without root.
Once system-level privileges are obtained, RedHook can silently install or remove applications, alter protected settings, and grant itself additional permissions without triggering confirmation dialogs. To remain active as long as possible, the trojan employs several anti-termination tactics: it simulates an active foreground window, plays silent audio, prevents the CPU from sleeping, and blocks the system from killing its process under low-memory conditions.
Two service processes monitor each other and restart their counterpart if either is stopped. After a device reboot, a dedicated component automatically restores all privileges. Stolen data and live screen recordings are transmitted over encrypted connections to attacker-controlled servers; when system rights are already present, the malware can stream the screen without triggering the standard screen-recording permission prompt.
Observed campaigns remain focused on Southeast Asia, with infections confirmed in Vietnam and later in Indonesia. Experts advise installing applications exclusively from official stores, scrutinizing permission requests—especially accessibility access—and remaining wary of unsolicited contacts claiming to represent banks or government agencies.
Related articles
Over 300 Tor Exit Nodes Hijacked to Intercept SSH Passwords and Deploy Ebury Backdoor
Attackers compromised hundreds of Tor exit nodes and repurposed them to perform man-in-the-middle attacks against SSH connections. Instead of reaching the intended server, users were redirected to attacker-controlled infrastructure where they could be tricked into accepting a forged host key and revealing their credentials. Researcher kaba identified 333 malicious exit nodes routing traffic through the same 12 interception servers after noticing an unexpected host-key warning on October 2. The campaign also attempted to install the Ebury Linux backdoor designed to steal authentication data. The Tor Project confirmed that operators' servers had their configurations altered and some middle relays were converted into exit nodes. The initial access vector remains unknown, but the activity window was limited to October 1-5. Users who connected via Tor during this period, accepted an unfamiliar key, and entered a password should treat their credentials as compromised.
LunaSpy Android Spyware Masquerades as FSB Antivirus and Bundles Right Dialer
Positive Technologies researchers discovered a malicious APK named Антивирус ФСБ.apk that installs the legitimate Right Dialer application from developer Goodwy while embedding the LunaSpy spyware. The sample uses package name com.syscore.toolsuite and requests extensive permissions including Accessibility Service to enable broad device control. Dynamic analysis in PT Sandbox revealed command-and-control communication, privilege escalation, and creation of hidden files. Static analysis showed XOR-encrypted strings and an expanded command set that includes call recording via CallService, call redirection rules in JSON format, screen tree extraction, gesture simulation, and anti-analysis commands such as RESET_REBOOT and DISABLE_PLAY_PROTECT. The malware can exfiltrate call recordings in WAV format, perform taps and swipes, and revive camera and microphone permissions through overlay notifications. Researchers published file and network indicators of compromise including multiple IP addresses used by the operators.
MegaFon Reports 34% Rise in Russian Mobile Malware Infections Driven by Android Trojans
MegaFon monitoring data shows a 34% year-over-year increase in Russian users with detected mobile malware during summer 2026, with the sharpest spike of 77% recorded in August. The growth is primarily attributed to Android trojans capable of installing apps without user consent, intercepting notifications, enabling remote access, and stealing personal data. At the same time, blocked suspicious calls dropped significantly, by 31% in June, 41% in July, and 75% in August, which the operator links to state and corporate anti-fraud measures. Scammers are adapting by hijacking messenger accounts through social engineering, malware, and even rental schemes, often combining calls with fake app installations that deploy spyware. Phishing remains active, with 30% of detected malicious resources tied to investments and crypto, 21% to social networks and messengers, and 9% to harmful APK files. Director Sergey Khrenov noted that smartphones are increasingly used as tools by the attackers themselves in these hybrid schemes.
Reflective DLL Injection: How Malware Executes DLLs Directly in Memory Without Disk Files
Reflective DLL Injection allows malicious code to load and execute a DLL entirely in memory, bypassing traditional file-based loading mechanisms on Windows. The technique uses a custom loader inside the DLL itself to handle PE format parsing, relocations, imports, TLS, and exception handling without calling LoadLibrary. Unlike standard loading, the resulting module often resides in MEM_PRIVATE regions and does not appear in conventional module lists, complicating forensic analysis. Tools such as Meterpreter and Cobalt Strike have historically employed reflective loaders, though Beacon Object Files represent a different COFF-based approach. Investigators must examine memory regions, thread start addresses, and Sysmon events 7, 8, and 10 rather than relying solely on file artifacts. The method does not bypass DEP, Arbitrary Code Guard, or access-control restrictions and leaves detectable traces when combined with behavioral indicators. Proper detection requires correlating private executable memory with process behavior and avoiding over-reliance on simplified signatures.