<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secrets on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/secrets/</link><description>Recent content in Secrets on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 01 Oct 2026 15:01:33 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/secrets/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Code Held 543,699 Working Keys and Passwords and the Oldest Dates Back to 2009</title><link>https://hackingpassion.com/github-leaked-keys-still-working/</link><pubDate>Thu, 01 Oct 2026 15:01:33 +0200</pubDate><guid>https://hackingpassion.com/github-leaked-keys-still-working/</guid><description>&lt;p>&lt;strong>543,699 keys and passwords sat in public GitHub code and still worked when researchers tested them in July 2026.&lt;/strong> The oldest went back to 2009. 51.8 percent were types GitHub&amp;rsquo;s default protection does not block.&lt;/p>
&lt;p>Researchers at Truffle Security went through &lt;strong>224 million public GitHub repositories&lt;/strong>. For each API key, cloud key, database password and token they found in the code, they asked the service that issued it if it still let them in. They did that on 27 and 28 July 2026, and &lt;strong>543,699 of them still worked&lt;/strong>.&lt;/p></description></item></channel></rss>