Skip to navigation

Threat reportMalwareTL-2026-0737

Android.MagicAd Trojan Floods Devices with Ads via Xiaomi GetApps, Samsung Galaxy Store, and Preinstalled Vivo / Amazon Fire TV Apps

mediumACTIVE

Android.MagicAd is an in-the-wild Android adware trojan that floods infected devices with persistent background advertisements while bypassing Android's overlay-permission and analysis-resistance controls. Doctor Web found it embedded in 50+ games and apps on Xiaomi's GetApps store and the Samsung Galaxy Store, in third-party APK mods on Apkmody/Moddroid, and as variants targeting Vivo smartphones and Amazon Fire TV devices, with infected titles rotated roughly monthly to evade detection.

Key facts

IdentifiersTL-2026-0737
Also known asAndroid.MagicAd.1, Android.MagicAd.1.origin, MagicAd
SeverityMEDIUM
Affected productsXiaomi GetApps app store (Android) / MIUI devices; Samsung Galaxy Store (Android); Vivo Vivo smartphones (preinstalled/system-app variant); Amazon Fire TV devices
Weaknesses (CWE)CWE-919, CWE-507, CWE-829
MalwareAndroid.MagicAd, Android.MagicAd.1, Android.MagicAd.1.origin
MITRE ATT&CK techniquesT1406.001 Steganography, T1406.002 Software Packing, T1407 Download New Code at Runtime, T1418 Software Discovery, T1422 System Network Configuration Discovery, T1426 System Information Discovery, T1437.001 Web Protocols, T1474.002 Compromise Hardware Supply Chain, T1474.003 Compromise Software Supply Chain, T1516 Input Injection, T1541 Foreground Persistence, T1575 Native API and 8 more in the attack flow
MotivationFINANCIAL
Target sectorsconsumer, retail, media, telecommunications
Target regionsGlobal, Asia, Europe, North America
Detection rules9 (1 shown free)
Sources8 cited sources

Detection coverage

As of 2026-06-09, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0737 across Splunk SPL, Microsoft KQL and Sigma, covering 22 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Android.MagicAd — Runtime Dex Load from Encrypted Native Library + Translucent-Activity Ad Render (Exploitation)

Detects the MagicAd execution trigger: at runtime the trojan decrypts an encrypted native library (libmagic_enc-style .so) in its resource/lib directory, extracts a dex into app_DynamicOptDex, loads it via DexClassLoader, then renders ad content as a floating Theme.Translucent Activity WITHOUT holding SYSTEM_ALERT_WINDOW. The pairing of runtime dex loading from a decrypted .so with a translucent floating activity that requests no overlay permission is the hallmark of MagicAd's initial ad-delivery exploitation and is rarely seen together in benign apps.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1407, T1406.002, T1437.001
  • Data sources: android_logcat, mobile_edr
  • Severity: high
  • Confidence: high

Splunk SPL

index=android sourcetype="android:logcat" (DexClassLoader OR InMemoryDexClassLoader OR app_DynamicOptDex OR decrypt_native OR libmagic_enc) OR ("Theme.Translucent" AND "windowIsFloating=true") 
| rex field=_raw "(?<pkg>com\.[a-zA-Z0-9_\.]+)/\.[A-Za-z]+" 
| eval dex_load=if(match(_raw,"DexClassLoader|InMemoryDexClassLoader|app_DynamicOptDex|decrypt_native|libmagic_enc"),1,0) 
| eval translucent_ad=if(match(_raw,"Theme\.Translucent") AND match(_raw,"windowIsFloating=true|AdTranslucentActivity"),1,0) 
| eval no_overlay=if(match(_raw,"permission=NONE"),1,0) 
| stats sum(dex_load) as dex_events sum(translucent_ad) as ad_events sum(no_overlay) as no_overlay_events values(_raw) as evidence by host pkg 
| where dex_events>0 AND ad_events>0 
| eval severity="high" 
| table host pkg dex_events ad_events no_overlay_events evidence

Microsoft KQL

AndroidLogcat_CL
| where TimeGenerated > ago(24h)
| where Message has_any ("DexClassLoader","InMemoryDexClassLoader","app_DynamicOptDex","decrypt_native","libmagic_enc") or (Message has "Theme.Translucent" and Message has "windowIsFloating=true")
| extend DexLoad = iff(Message has_any ("DexClassLoader","InMemoryDexClassLoader","app_DynamicOptDex","libmagic_enc"),1,0)
| extend TranslucentAd = iff(Message has "Theme.Translucent" and (Message has "windowIsFloating=true" or Message has "AdTranslucentActivity"),1,0)
| summarize DexEvents=sum(DexLoad), AdEvents=sum(TranslucentAd), Evidence=make_set(Message,20) by DeviceName, _ResourceId
| where DexEvents > 0 and AdEvents > 0
| project DeviceName, DexEvents, AdEvents, Evidence

Sigma

title: Android.MagicAd Runtime Dex Load and Translucent Ad Render
id: 6f3c9a21-8b4d-4e57-9c1a-1d2e3f4a5b61
status: experimental
description: Detects MagicAd extracting a dex from a decrypted native library and rendering ads via a floating translucent activity without SYSTEM_ALERT_WINDOW.
references:
    - https://news.drweb.com/show/?i=15262&lng=en
    - https://attack.mitre.org/techniques/T1407/
author: Threadlinqs Team
date: 2026/06/09
tags:
    - attack.execution
    - attack.t1407
    - attack.defense_evasion
    - attack.t1406.002
    - attack.command_and_control
    - attack.t1437.001
logsource:
    product: android
    category: application
detection:
    dex_load:
        Message|contains:
            - 'DexClassLoader'
            - 'app_DynamicOptDex'
            - 'libmagic_enc'
            - 'decrypt_native'
    translucent_ad:
        Message|contains|all:
            - 'Theme.Translucent'
            - 'windowIsFloating=true'
    condition: dex_load and translucent_ad
falsepositives:
    - Legitimate apps using DexClassLoader for plugin frameworks combined with splash/overlay UIs
level: high

Known false positives:

  • Legitimate apps that load plugins via DexClassLoader and also display floating splash/overlay screens
  • Game engines extracting optimized dex at first launch

Tuning notes: Baseline the set of packages legitimately using DexClassLoader in your fleet and allowlist them. Raise fidelity by requiring the dex path to resolve under app_DynamicOptDex AND the source library name to match an *_enc.so pattern in the resource/lib directory.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Android.MagicAd — Anti-Analysis Gating Before Ad Delivery (Exploitation Pre-Check) · unlock with TL Creds
  • Android.MagicAd — Silent Foreground Service Persistence via Notification Channels (Post-Exploitation) · unlock with TL Creds
  • Android.MagicAd — Ad-Network Beaconing and Traffic Generation Over Web Protocols (C2 / Lateral) · unlock with TL Creds
  • Android.MagicAd — Translucent-Activity Overlay-Permission Bypass Ad Render (Exploitation) · unlock with TL Creds
  • Android.MagicAd — Masquerading Trojanized App with Suppressed Icon (Post-Exploitation / Defense Evasion) · unlock with TL Creds
  • Android.MagicAd — Watchdog Scheduled-Task Service Re-spawn (C2 / Persistence-driven Ad Loop) · unlock with TL Creds
  • Android.MagicAd — Launcher Icon Suppression with Watchdog Service Re-spawn (Post-Exploitation) · unlock with TL Creds
  • Android.MagicAd — System-App Intent/Binder Abuse and Zero-Volume Media Ad Trigger (C2 / Ad Delivery) · unlock with TL Creds

Indicators of compromise

As of 2026-06-09, Threadlinqs Intelligence tracks 22 indicators of compromise for TL-2026-0737.

Sample indicators (1 of 22)

  • URL: hxxps://github[.]com/DoctorWebLtd/malware-iocs

Defanged, TLP:CLEAR. Full set of 22 indicators: unlock with TL Creds.

22 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Android.MagicAd (Doctor Web detections Android.MagicAd.1 and its dex component Android.MagicAd.1.origin) is a mobile adware/ad-fraud trojan first observed in the wild in 2025 and detailed in Doctor Web's Q1 2026 mobile virus-activity review. Its primary objective is monetization through aggressive, unsolicited advertising rather than data theft, but its evasion and persistence engineering make it notable as a widely distributed mobile threat warranting dedicated detection coverage.

Distribution is multi-channel and abuses trusted supply chains. Doctor Web found MagicAd concealed in more than 50 games and programs on Xiaomi's official GetApps catalog, with additional variants on the Samsung Galaxy Store. The operators rotated their uploads: an infected app typically remained available for roughly one month before being pulled and replaced with a freshly uploaded title, a tactic that both extends campaign lifetime and frustrates signature-based takedowns. The trojans were also pushed through third-party APK sites such as Apkmody and Moddroid, frequently masquerading as modified ('mod') builds of popular services. Beyond app-store delivery, MagicAd appeared as device-specific variants on Vivo smartphones and Amazon Fire TV devices, indicating compromise or abuse of preinstalled/system-app channels on those platforms.

Part of MagicAd's malicious functionality is hidden inside encrypted native libraries stored in the app's resource directory. At runtime the trojan decrypts these libraries, extracts dex components from them, and executes the embedded modules — keeping the malicious logic out of static view of store-vetting and many scanners. Before displaying any ads, MagicAd performs environment-safety checks: it searches for virtual-machine / emulator artifacts, verifies whether the installation appears 'organic' (a real user install rather than an automated/analysis install), and filters the device's IP address against a blacklist, suppressing activity in suspected analysis environments.

MagicAd's defining trait is displaying advertisements without requesting the SYSTEM_ALERT_WINDOW permission that normally gates screen overlays. Instead it renders ad banners as Translucent Activity windows, which surface on screen without triggering the usual overlay-permission checks. To reach and wake system surfaces, it sends crafted Intents (including pending intents) to built-in apps that process intents even when not explicitly launched: on Xiaomi devices it targets Mi Browser and the MIUI SystemUI shell; on Amazon devices it leverages the Fire TV Home Screen launcher; on Vivo devices it uses the lower-level Android Binder channel against iManager, Phonebook, Vivo Browser, and a customized Baidu IME. A platform-agnostic fallback decrypts an audio file embedded in the trojan's body, writes it to its working directory, launches the system media player at zero volume, and simulates button presses to silently trigger ad playback/interaction.

For persistence the trojan hides its launcher icon from the app menu, spawns multiple silent background/foreground services backed by notification channels, and registers task-scheduler 'watchdog' jobs that periodically restart its services. On older Android versions it can launch a virtual screen to keep itself alive and prevent the system from shutting it down. Multiple fallback methods with retry logic ensure the ad-delivery and persistence loops continue even after the originating app is removed from a store. Defenders should treat MagicAd primarily as an ad-fraud / resource-abuse and trust-erosion threat on Android, Vivo, and Fire TV estates and prioritize behavioral detection (icon hiding, translucent-activity ad rendering, runtime dex loading from encrypted native libs, watchdog re-spawn, and intent abuse against system apps).

MITRE ATT&CK techniques by tactic:

Defense Evasion

T1406.001 Steganography; T1406.002 Software Packing; T1628.001 Suppress Application Icon; T1628.002 User Evasion; T1633.001 System Checks; T1655.001 Match Legitimate Name or Location

defense-evasion

T1407 Download New Code at Runtime

Discovery

T1418 Software Discovery; T1422 System Network Configuration Discovery; T1426 System Information Discovery

Command and Control

T1437.001 Web Protocols

Initial Access

T1474.002 Compromise Hardware Supply Chain; T1474.003 Compromise Software Supply Chain; T1660 Phishing

Impact

T1516 Input Injection; T1643 Generate Traffic from Victim

Persistence

T1541 Foreground Persistence; T1603 Scheduled Task/Job; T1624.001 Broadcast Receivers

Execution

T1575 Native API

Remediation

Immediate actions

  • Uninstall apps flagged as Android.MagicAd.1 / Android.MagicAd.1.origin and any recently installed games or modified 'pro/plus' app builds that hide their icon or show out-of-context full-screen ads
  • Block and remove sideloaded APKs sourced from third-party sites such as Apkmody and Moddroid via MDM policy
  • On managed Android/Vivo/Fire TV fleets, audit for apps spawning persistent background services with hidden launcher icons

Workarounds

  • Disable sideloading / unknown-sources installation
  • Review and revoke ability of non-system apps to launch foreground services and schedule background tasks where MDM allows
  • Remove preinstalled bloat/system apps that are abused as ad-surface targets where the platform permits

Longer-term hardening

  • Deploy a reputable mobile EDR/AV with behavioral detection for runtime dex loading, translucent-activity ad rendering, and icon hiding
  • Restrict installs to vetted enterprise app catalogs and disable installation from unknown sources via MDM
  • Enable Google Play Protect and keep it on; monitor for re-uploaded clones of removed titles
  • Educate users not to install 'modded' versions of Spotify, YouTube, Deezer, Netflix and similar apps

Affected and fixed versions

  • Xiaomi — GetApps app store (Android) / MIUI devices
    Vulnerable versions: 50+ trojanized games and apps distributed via GetApps
  • Samsung — Galaxy Store (Android)
    Vulnerable versions: Android.MagicAd variants distributed via Galaxy Store
  • Vivo — Vivo smartphones (preinstalled/system-app variant)
    Vulnerable versions: Variant abusing iManager, Phonebook, Vivo Browser, Baidu IME Customized via Binder
  • Amazon — Fire TV devices
    Vulnerable versions: Variant abusing Fire TV Home Screen launcher

Timeline

  • Android.MagicAd first appears in the wild, distributed through legitimate and third-party Android app sources (Doctor Web, year-of-first-observation per Q1 2026 review).
  • Android.MagicAd embedded in more than 50 games and programs on Xiaomi's official GetApps catalog, with infected titles rotated roughly monthly to evade takedown.
  • Variants identified on the Samsung Galaxy Store and distributed via third-party APK sites Apkmody and Moddroid as modified versions of popular apps.
  • Device-specific variants observed targeting Vivo smartphones (abusing iManager, Phonebook, Vivo Browser, Baidu IME via Binder) and Amazon Fire TV devices (abusing the Fire TV Home Screen launcher).
  • Public reporting (The420 and others) highlights Dr.Web findings on Android ad-fraud trojans abusing Xiaomi GetApps.
  • Doctor Web documents Android.MagicAd in its Q1 2026 mobile virus-activity review, detailing translucent-activity ad rendering, encrypted native-library dex loading, and watchdog persistence.
  • Doctor Web releases Android.MagicAd indicators of compromise via its public malware-iocs GitHub repository (github.com/DoctorWebLtd/malware-iocs) for defender consumption.
  • Doctor Web publishes its dedicated Android.MagicAd advisory (news.drweb.com/show/?i=15262) describing per-device ad-display techniques, SYSTEM_ALERT_WINDOW bypass, system media-player abuse, and the abuse of built-in apps (Mi Browser, MIUI SystemUI, Fire TV launcher, Vivo iManager/Phonebook/Browser/Baidu IME).
  • Wider security press (Cyber Security News, GBHackers) publish detailed analyses of Android.MagicAd; threat tracked as ACTIVE.

Sources cited

Previous and next in malware

Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats