Malicious Perplexity Chrome Extension Intercepted Searches and Address Bar Input

Malicious Perplexity Chrome Extension Intercepted Searches and Address Bar Input

Malicious Perplexity Chrome Extension Intercepted Searches and Address Bar Input

https://thehackernews.com/2026/06/malicious-perplexity-chrome-extension.html

Publish Date: 2026-06-29 14:40:00

Source Domain: thehackernews.com

Swati KhandelwalJun 29, 2026Browser Security / Web Security

Microsoft has found a malicious Chrome extension that posed as the AI search engine Perplexity and quietly logged what people searched for. It routed every query and every character typed into the address bar through an attacker-controlled server before redirecting users to real results.

Microsoft says Google removed it from the store after responsible disclosure. The extension was called “Search for perplexity ai” (ID flkebkiofojicogddingbdmcmkpbplcd) and used a look-alike domain, perplexity-ai[.]online, to pass for the real service at perplexity.ai.

Microsoft’s Defender research team says the point was to intercept searches and collect data. It found no proof of password theft, but far more access than a search box should ever need.

Once installed, the extension sets itself as the browser’s default search engine. When you searched, the query went first to perplexity-ai[.]online, where the attacker’s server logged it with your browser headers, IP address, and user agent.

A rule then bounced you to a real search engine (Perplexity, Google, or Bing), so the results looked normal. The theft happened on that first stop, before the redirect.

The address bar made it worse. The extension also pointed the browser’s live search suggestions (the suggest_url) to the same attacker domain. So your input went to the attacker’s server before you pressed Enter. Not just finished searches, but every character as you typed it.

Chrome permits search-provider overrides, and legitimate extensions use them. Rewriting and redirecting your traffic is the part a search box has no business doing. This one asked for the declarativeNetRequest family of permissions to do exactly that, then shipped server-side code that logged every request. Microsoft calls that proof the collection was deliberate, not a side effect of the redirect.

The extension also shipped disabled redirect rules for Google and Bing, so the…

Source