<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Some old news, but always relevant, so we don&#x27;t forget our OpSec:]]></title><description><![CDATA[<p>Some old news, but always relevant, so we don't forget our OpSec:</p><p>I hope y'all have seen the Urban VPN "scandal" by now.</p><p>If you haven't caught up, it wasn't just a VPN, it was effectively a wiretap.</p><p>Their browser extension was found intercepting AI chats (ChatGPT, Claude, etc.) by overriding the fetch() function.</p><p>They weren't just logging IPs, they were stealing the actual content of your prompts to sell to data brokers. But the real lesson here isn't just "don't use Urban VPN." </p><p>It’s about OpSec 101: Never trust a centralized entity. <br />If you care about security, the rule is simple: Don't trust, verify.</p><p>The moment you hand your traffic to a centralized company, especially a "free" one, you’ve created a single point of failure. </p><p>A VPN is just someone else's computer. If you don't own the infrastructure, you don't own your privacy.</p><p>Stop looking for "trustworthy" companies and start building a "zero trust" mindset.</p><p>The only way to ensure you aren't the product is to use a system where no one has the power to sell you out. Don't trust. Verify. Decentralize.</p><p><a href="https://infosec.exchange/tags/ph4ntxm" rel="tag">#<span>ph4ntxm</span></a> <a href="https://infosec.exchange/tags/linux" rel="tag">#<span>linux</span></a> <a href="https://infosec.exchange/tags/debian" rel="tag">#<span>debian</span></a> <a href="https://infosec.exchange/tags/os" rel="tag">#<span>os</span></a> <a href="https://infosec.exchange/tags/live" rel="tag">#<span>live</span></a> <a href="https://infosec.exchange/tags/privacy" rel="tag">#<span>privacy</span></a> <a href="https://infosec.exchange/tags/security" rel="tag">#<span>security</span></a>  <a href="https://infosec.exchange/tags/opsec" rel="tag">#<span>opsec</span></a> <a href="https://infosec.exchange/tags/infosec" rel="tag">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/research" rel="tag">#<span>research</span></a> <a href="https://infosec.exchange/tags/tech" rel="tag">#<span>tech</span></a> <a href="https://infosec.exchange/tags/technology" rel="tag">#<span>technology</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/20b75794-9afc-4d22-8975-fdc3c1ed20b4/some-old-news-but-always-relevant-so-we-don-t-forget-our-opsec</link><generator>RSS for Node</generator><lastBuildDate>Mon, 25 May 2026 01:48:06 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/20b75794-9afc-4d22-8975-fdc3c1ed20b4.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 16 May 2026 19:00:13 GMT</pubDate><ttl>60</ttl></channel></rss>