AI 产品解读Search engine override that redirects Chrome omnibox searches to Yahoo search engine via defaultsearch.co
Provides a search monetization layer by intercepting browser searches and routing them through a partner search proxy (defaultsearch.co) that ultimately serves Yahoo search results, generating affiliate revenue for Lavasoft/Adaware
1. User installs extension. 2. Extension sets defaultsearch.co as Chrome's default search engine via chrome_settings_overrides manifest permission. 3. When user types a search query in Chrome's omnibox, the query is redirected to https://defaultsearch.co/?sp=11&q={searchTerms} which serves Yahoo search results. 4. Background service worker collects telemetry (install, update, daily activity) and sends to flow.lavasoft.com. 5. Extension popup shows only Privacy Policy and Terms links.
Overrides Chrome's default search engine via chrome_settings_overridesRedirects omnibox searches to Yahoo via defaultsearch.co proxyTelemetry and analytics tracking (install events, daily activity, update events)Tracks installation attribution parameters (partner ID, campaign ID, source traffic)
- 目标用户
- Users who install this extension (often bundled or installed via partner distribution channels) / General Chrome users seeking search functionality
- Cannot verify what defaultsearch.co actually serves (Yahoo results or ads) without live testing
- Cannot confirm if Yahoo search results include ads or affiliate monetization
- The extension's actual search experience and result quality cannot be assessed from source code alone
付费分析未识别到付费功能
No paid features, subscriptions, or payment flows exist in the extension. All 'pro' keyword matches are false positives: 'productId' (product identifier string), 'preProd' (boolean flag), 'Promise' (JavaScript built-in), 'Object.getOwnPropertyNames' (JS method). 'license' matches are from the GPL LICENSE.txt. No billing, payment, subscription, or upgrade UI or API calls exist.
- 置信度
- 95
- 支付平台
- --
- 来源
- AI / 高
- 需要登录
- 否
- 登录理由
- No login functionality exists. The extension does not implement authentication UI, does not redirect to any login page, and does not require user accounts to use. The 'auth' keyword matches in httpUtil.js are generic HTTP authorization header parameters, not login flows.