Esc
SafetyEmerging

Banned AI chat-stealing extension returns to Chrome Store

Is this a scandal?

Not yet — an early signal. Noise 47/100, heating up, across 2 sources.

SCAND-192695as of Methodology
Cite this incident"Banned AI chat-stealing extension returns to Chrome Store." SCAND.Ai incident SCAND-192695, noise 47/100 as of August 11, 2026. https://scand.ai/scandal/banned-ai-chat-stealing-extension-returns-chrome-store
FORECASTForecast, not fact

Google will likely implement stricter re-submission checks for previously banned developers because recurring policy violations damage platform trust and invite regulatory scrutiny.

47

Noise 47/100 — louder than 99% of tracked AI controversies.

AI-assisted analysis · How we work

Why it matters

This incident exposes critical gaps in browser extension vetting, threatening user privacy as AI adoption grows and highlighting risks of supply chain attacks on LLM interfaces.

Key points

  1. Extension previously banned for stealing AI chat data was reinstated to Chrome Web Store
  2. Malicious extension amassed over 300,000 installs with 4.6-star rating before removal
  3. Researchers confirm reinstated extension resumed unauthorized AI conversation exfiltration
  4. Recurrence indicates insufficient post-ban enforcement in Chrome extension review process
  5. SecurityWeek reported the return and continued malicious activity of the extension

The story

A Chrome extension previously removed by Google for exfiltrating AI chat data has returned to the official store and resumed malicious activities, according to SecurityWeek. The extension had accumulated over 300,000 installs and a 4.6-star rating before its initial ban for unauthorized data collection. Researchers report the reinstated version continues stealing sensitive conversations from generative AI platforms despite prior enforcement action. This recurrence suggests inadequate post-removal monitoring within the Chrome Web Store ecosystem. The incident highlights persistent vulnerabilities in browser extension security reviews that allow bad actors to evade permanent bans. Users who reinstalled or newly downloaded the extension after its return are potentially exposed to ongoing data theft. Google has not yet commented on the specific reinstatement mechanism or new mitigation measures. Security experts warn this pattern undermines trust in official distribution channels for AI-integrated tools.

Who's involved

Critic
SecurityWeek

Reports that the reinstated extension resumed stealing AI chat data despite prior ban

Critic
Shah Sheikh

Amplified SecurityWeek findings to warn users about the extension's return and ongoing risks

Defender
Google

Previously removed the extension for policy violations but allowed reinstatement without preventing recurrence

How the conversation shifted

opinion has hardened

Polarity (0–100) from the noise pipeline, sampled over time.

Join the Discussion

Discuss this story

Community comments coming in a future update

Be the first to share your perspective. Subscribe to comment.

Noise Level

Buzz47?Noise Score (0–100): how loud a controversy is. Composite of reach, engagement, star power, cross-platform spread, polarity, duration, and industry impact — with 7-day decay.
Decay: 99%
Reach
38
Engagement
77
Star Power
40
Duration
13
Cross-Platform
50
Polarity
50
Industry Impact
50

The timeline

  1. Shah Sheikh amplifies report on Twitter

    Shared SecurityWeek article warning followers about extension returning to Chrome Store

  2. SecurityWeek reports extension return

    Article published documenting reinstatement and resumed malicious activity of banned AI chat stealer

The full record

Sources & methodology

Every claim above traces to these primary items. How we score →

The forecast

Google will likely implement stricter re-submission checks for previously banned developers because recurring policy violations damage platform trust and invite regulatory scrutiny.

Forecast, not fact — an editorial estimate we score when this resolves.

You're up to date

That's the complete picture as of — nothing more to know right now. We'll update this page the moment it changes.

Follow this story

We keep this page current — no need to check back. We'll send the next real change to your inbox, nothing else.

Tracking this story since August 11, 2026.