<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Extensions on CuraSec</title><link>https://curasec.metacog.co.kr/tags/extensions/</link><description>Recent content in Extensions on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 03 Aug 2026 13:48:19 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/extensions/index.xml" rel="self" type="application/rss+xml"/><item><title>Chrome to block policy-installed New Tab hijacker extensions</title><link>https://curasec.metacog.co.kr/insights/2026-08-03-google-chrome-may-soon-block-new-tab-hijacker-extensions-by/</link><pubDate>Mon, 03 Aug 2026 13:48:19 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-03-google-chrome-may-soon-block-new-tab-hijacker-extensions-by/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Review any policy-deployed Chrome extensions that control the New Tab page or default search engine before this change ships; audit enterprise extension policies to avoid unexpected breakage.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>