<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Adware on CuraSec</title><link>https://curasec.metacog.co.kr/tags/adware/</link><description>Recent content in Adware on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 29 Oct 2026 17:24:45 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/adware/index.xml" rel="self" type="application/rss+xml"/><item><title>Chrome extensions with 13.4M installs caught hijacking searches</title><link>https://curasec.metacog.co.kr/insights/2026-10-29-chrome-extensions-with-13-4-million-installs-caught-hijackin/</link><pubDate>Thu, 29 Oct 2026 17:24:45 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-29-chrome-extensions-with-13-4-million-installs-caught-hijackin/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Enterprises with unmanaged Chrome deployments have real exposure here. Obtain the list of 319 extension IDs from BleepingComputer&amp;rsquo;s reporting, audit managed Chrome environments via the Extension Management policy, and blocklist or remove any matches.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Retrieve the tracking/redirect domains associated with the campaign and create proxy or DNS detections for search queries being routed through third-party advertising servers; also sweep historic proxy logs for hits against those domains since installation dates.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A 13.4M-install adware campaign is a useful data point for justifying a browser extension governance policy — this reinforces the case for allowlisting or vetting Chrome extensions in managed enterprise environments, but there is no immediate leadership action unless internal exposure is confirmed.&lt;/li>
&lt;/ul></description></item></channel></rss>