Skip to main content
Mallory
Malware

Mzmess

Tracked since Nov 25, 2025 · Updated 5 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns0Associated
Actors0Associated
ATT&CK0Techniques
IOCs0Tracked

Mzmess is an Android malware family and plugin framework associated with malicious activity on Android-based smart TVs, set-top boxes, and other embedded consumer devices. It has been observed as a modular component delivered in environments linked to the Vo1d ecosystem, where it is used to load additional functionality through dynamically executed DEX code. Security reporting has described Mzmess as part of a broader monetization-oriented operation involving compromised Android media devices at large scale.

The malware is characterized by a plugin-based architecture centered on a DexLoader component that retrieves and executes secondary modules. Reported modules include proxy-related functionality, including delivery of the Popa proxy plugin, as well as components associated with traffic inflation and ad-fraud style abuse. This modular design allows operators to repurpose infected devices for different revenue-generating tasks without replacing the core implant.

Mzmess has been linked to suspicious boot-time payload delivery on certain Android-based digital picture frames running the Uhale platform. In those cases, an updated application was observed downloading JAR or DEX artifacts and executing them persistently on subsequent boots. Similarities in package naming, strings, endpoints, delivery workflow, and artifact placement have been cited as evidence of a connection between those payloads, Mzmess, and the Vo1d malware ecosystem, although the precise relationship between Mzmess and Vo1d has not been fully resolved.

Targeting appears focused on poorly secured Android consumer devices, especially smart TVs, set-top boxes, and rebranded embedded products that may ship with insecure defaults such as disabled SELinux, root access, weak update security, or trust failures that enable remote code execution. In operational use, Mzmess-enabled infections support proxy infrastructure and fraudulent traffic generation, turning compromised devices into monetizable network assets. The malware is therefore notable both for its modular Android execution model and for its role in large-scale abuse of internet-connected media devices.

Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matchingMatch every observed IP, domain, and hash against your live telemetry.
Associated threat actorsGroups linked to this family, with evidence pinned to each claim.
Associated vulnerabilitiesCVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mappingEvery documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.