<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>I Spy with My Little Eye: Analysis and Detection of Spying Browser Extensions · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1612.00766/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1612.00766/feed.xml" rel="self" type="application/rss+xml" /><item><title>I Spy with My Little Eye: Analysis and Detection of Spying Browser Extensions — mentioned by ThePhysicist</title><link>https://news.ycombinator.com/item?id=14892519</link><guid isPermaLink="false">urn:hackerpapers:mention:1612.00766:14892519</guid><pubDate>Mon, 31 Jul 2017 14:53:18 GMT</pubDate><description>&lt;p&gt;We were only able to name one extension (the one named in the presentation), as we did not have conclusive proof that data from other extensions which we found to be suspicious ended up in the data set (as the access to incremental data was limited to a short time period): We developed a sandboxing framework to test whether Chrome extensions send URL data to a third party using a MITM proxy, the code is available on Github: https://github.com/adewes/chrome-extension-behavior-analysis There&amp;#x27;s also a large study on this that uses a very similar technique: https://arxiv.org/pdf/1612.00766.pdf In…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1612.00766/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
