Is MapQuest Search safe?
MapQuest Search is high risk. Code analysis shows the extension sets itself as default search provider; address bar suggestions send each partial query to mapquestdrivingdirections.org. This was not observed at runtime.…
MapQuest Search findings
Default search sends address bar keystrokes to mapquestdrivingdirections.org
Code analysis shows the extension sets itself as default search provider; address bar suggestions send each partial query to mapquestdrivingdirections.org.
This was not observed at runtime.
What actually happens
You type a search into the browser address bar.
The browser sends the partial text to mapquestdrivingdirections.org for suggestions.
Data sent per suggestion request
- Partial search textpizza near
Whatever you have typed so far, sent before you press enter.
- Request addresshttps://mapquestdrivingdirections.org/admin-search/public/autosuggest?searchTerm=pizza%20near
Tells the site which endpoint serves suggestions.
The code that does this
Search provider declaration in the manifest
Same declaration; no obfuscation, manifest is plain JSON
manifest.json"chrome_settings_overrides": { "search_provider": { "name": "Online", "keyword": "MapQuest", "search_url": "https://mapquestdrivingdirections.org/admin-search/public/link?q={searchTerms}", "suggest_url": "https://mapquestdrivingdirections.org/admin-search/public/autosuggest?searchTerm={searchTerms}", "favicon_url": "https://mapquestdrivingdirections.org/admin-search/public/favicon.ico", "encoding": "UTF-8", "is_default": true }}Destination of suggestion requests
- mapquestdrivingdirections.org
Receives partial queries and serves search results; operator not identified in the manifest.
Observation
Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.
Search queries routed through monetization funnel with per-install tracking
Every address-bar search routes through mapquestdrivingdirections.org before reaching Yahoo's infospace search.
A campaign ID matching the install ID and an install-date stamp let the operator attribute searches and link history.
What actually happens
You type a search query into the browser address bar and press Enter.
The extension has replaced the default search engine via chrome_settings_overrides.search_provider, so all omnibox searches are directed through its endpoint.
The extension injects your unique install ID and the date you first installed it into every search request before it leaves your browser.
A declarativeNetRequest dynamic rule appends campaignid=<extension-runtime-id> and installdate=<YYYYMMDD> to each request matching mapquestdrivingdirections.org/admin-search/public/link, then the operator's server forwards the query to Yahoo infospace.
Captured request
Yahoo search results page for the planted marker query. The intermediate request to mapquestdrivingdirections.org was server-side redirected; the Yahoo destination with query terms and infospace affiliate parameters was captured in dynamic analysis.
Tracking parameters injected on every search request
- Install ID (campaignid)onpkagahfdnlknakhgnegpipmhkodnlm
A fixed identifier tied to your browser install. Lets the operator link all your searches across sessions and days, even without login.
- Install date (installdate)20240315
The date you first installed the extension, as YYYYMMDD. Stored locally and attached to every search so the operator knows your tenure.
- Search query (q / p)cheap flights london to new york
The words you typed into the address bar. Delivered first to the operator's domain and then forwarded to Yahoo's infospace service.
The code that does this
DNR rule injects tracking parameters on every search, background.js
const extensionDomain = 'mapquestdrivingdirections.org', campaignid = chrome.runtime.id;const getTracking = () => new Promise(r => chrome.storage.sync.get(r));const setUpSearchUrl = async () => { const { installdate } = await getTracking(); await chrome.declarativeNetRequest.updateDynamicRules({ removeRuleIds: [1], addRules: [ { id: 1, priority: 1, action: { type: "redirect", redirect: { transform: { queryTransform: { addOrReplaceParams: [ { key: "campaignid", value: campaignid }, { key: "installdate", value: installdate || new Date().toISOString().split('T')[0].replace(/-/g, '') }, ] } } } }, condition: { urlFilter: "mapquestdrivingdirections.org/admin-search/public/link", resourceTypes: ["main_frame"] } } ] });};Destinations receiving search data
- mapquestdrivingdirections.org
Operator-controlled intermediary. Receives every search query plus campaignid and installdate tracking parameters. Redirects requests to Yahoo infospace on the server side.
- uk.search.yahoo.com
Yahoo infospace search results endpoint. Final destination for queries; affiliate parameters (hspart=infospace, hsimp=yhs-090) indicate the operator earns per-search revenue.
If you have MapQuest Search installed
- Open
chrome://extensionsand turn on Developer mode to show IDs. Find the one with IDonpkagahfdnlknakhgnegpipmhkodnlmand choose Remove. - Scan your browser to check the rest of your extensions.
What MapQuest Search can do
Permissions this extension asks for, as declared in version 1.6. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on mapquestdrivingdirections.org
*://mapquestdrivingdirections.org/*
Store data in your browser
storage
Block and redirect the requests your browser makes
declarativeNetRequest
Chrome Web Store listing
- Versions
- 1.6 seen since March 4, 2026
- Store rating
- 2.0 from 4 ratings
- Last updated
- October 29, 2024
- Size
- 14.6 KiB
- Privacy policy
- system1.com
