<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hackers on Locodigital</title><link>https://locodigital.com.br/en/tags/hackers/</link><description>Recent content in Hackers on Locodigital</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 12 Sep 2026 09:00:00 -0300</lastBuildDate><atom:link href="https://locodigital.com.br/en/tags/hackers/index.xml" rel="self" type="application/rss+xml"/><item><title>Yahoo breach 2013: the biggest leak in history, explained</title><link>https://locodigital.com.br/en/technology/yahoo-breach-2013-the-biggest-leak-in-history/</link><pubDate>Sat, 12 Sep 2026 09:00:00 -0300</pubDate><guid>https://locodigital.com.br/en/technology/yahoo-breach-2013-the-biggest-leak-in-history/</guid><description>&lt;p&gt;In August 2013, someone broke into Yahoo's servers and copied the data of every user registered with the service. Three years later the company still did not know — or at least that is what it told the world. When the truth finally came out, in October 2017, the final number was staggering: &lt;strong&gt;3 billion accounts compromised&lt;/strong&gt;. To this day it remains the largest publicly confirmed data breach ever.&lt;/p&gt;
&lt;h2&gt;How the intrusion happened&lt;/h2&gt;
&lt;p&gt;The 2013 attack exploited Yahoo's internal authentication system. Rather than stealing passwords — which would have meant cracking them one by one — the intruders &lt;strong&gt;forged session cookies&lt;/strong&gt;. A session cookie is the file your browser keeps after you log in; it is what tells the site "this one already authenticated, let them through". With access to the server keys, you can mint a fake cookie that Yahoo accepted as legitimate.&lt;/p&gt;</description></item></channel></rss>