Bitdefender identified Midnight Mimosa, a campaign involving malware preinstalled in the firmware of thousands of inexpensive Android phones sold worldwide, leaving devices compromised before users first turned them on. Running with system-level privileges, the malware installs applications that generate fraudulent advertising impressions and automated clicks. It also collects device information and includes capabilities that could support botnet participation. Researchers detected affected devices in more than 150 countries over roughly two years.
The investigation also identified 13 Google Play apps that shared infrastructure and ad-fraud code with the campaign, connecting the firmware-based operation to applications distributed through Google's marketplace. The point at which the devices were compromised in the supply chain remains unknown. Although firmware certificates bore Shenzhen Zediel's name, that evidence does not establish that the company created or knowingly distributed the malware. The findings highlight a procurement risk: affected phones arrive with system-level malware already embedded, rather than becoming infected solely through user-installed applications.

Trace attribution and downstream blast radius.
6 events from the most recent confirmed update back to the earliest known activity.
Bitdefender corrected its initial identification of 85.17.70.38:6000 as a live proxyware command server, identifying it instead as a sinkhole. The address is therefore not confirmed attacker-controlled infrastructure.
Bitdefender identified com.mobile.applock.en as a dedicated TCP proxy that enrolls infected phones as relay nodes without advertisements or a user interface. The payload connects over TCP port 6000, rotates among four domains, and forwards traffic between its controller and server-designated targets.
Bitdefender reported that Midnight Mimosa temporarily disables Google Play during payload installations, suppressing installation prompts and blinding Play Protect before re-enabling Google Play. Its report also includes an extensive list of indicators of compromise.
Bitdefender identified 13 Google Play applications sharing infrastructure and ad-fraud code with the campaign. These apps provided genuine utility functions but could display advertisements outside their interfaces, without the firmware malware's system-level privileges.
Over roughly two years, Bitdefender detected the campaign on thousands of devices across more than 150 countries and identified at least 32 disguised payload applications. Researchers disclosed that the preinstalled malware could install or remove apps, grant permissions, and download and execute additional code; its supply-chain entry point remained unknown.
Phones from multiple brands using MediaTek chips were sold with malicious software already embedded in their firmware. The system-privileged malware silently installed utility-style applications that generated fraudulent advertising impressions and automated clicks.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. View all 146 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
9 references tracked. Mallory keeps watching after this page renders.
helpnetsecurity.com
Open sourcecryptika.com
Open sourcecybersecuritynews.com
Open sourcesecurityaffairs.com
Open sourcescworld.com
Open sourcesecurityweek.com
Open sourcehackread.com
Open sourcetherecord.media
Open sourcebitdefender.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.