<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>API-Security on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/api-security/</link><description>Recent content in API-Security on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 23 May 2026 15:04:37 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/api-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Google API Keys Keep Working for 23 Minutes After You Delete Them</title><link>https://hackingpassion.com/google-api-key-23-minutes/</link><pubDate>Sat, 23 May 2026 15:04:37 +0200</pubDate><guid>https://hackingpassion.com/google-api-key-23-minutes/</guid><description>&lt;p>Google tells you the key is gone. It keeps working for &lt;strong>23 more minutes&lt;/strong>. When you delete a Google API key, a dialog appears that says the following: &lt;em>&amp;ldquo;Once deleted, it can no longer be used to make API requests.&amp;rdquo;&lt;/em> That is the message. It is printed there by Google, presented as fact at the exact moment you think the risk is gone. It is not true.&lt;/p>
&lt;p>Security researcher &lt;strong>Joe Leon&lt;/strong> at &lt;strong>Aikido Security&lt;/strong> spent two days testing what actually happens after a key is deleted. He created keys, deleted them, and kept firing authenticated requests at Google&amp;rsquo;s servers at three to five per second until no valid response came back. He ran ten separate trials. The shortest window before a deleted key fully stopped working was nearly &lt;strong>eight minutes&lt;/strong>. The median was &lt;strong>sixteen minutes&lt;/strong>. The longest was just under &lt;strong>twenty-three minutes&lt;/strong>. During all of that time, the key was authenticating successfully on Google&amp;rsquo;s infrastructure. A deleted key. Still working.&lt;/p></description></item><item><title>How the Moltbook Database Breach Exposed 770,000 AI Agents</title><link>https://hackingpassion.com/moltbook-database-breach-exposed-ai-agents/</link><pubDate>Sun, 01 Feb 2026 15:15:32 +0100</pubDate><guid>https://hackingpassion.com/moltbook-database-breach-exposed-ai-agents/</guid><description>&lt;h1 id="how-the-moltbook-database-breach-exposed-770000-ai-agents">How the Moltbook Database Breach Exposed 770,000 AI Agents&lt;/h1>
&lt;p>Moltbook, the social network exclusively for AI agents, had its entire database wide open. 770,000 agents. Every API key exposed. Anyone could hijack any account and post whatever they wanted.&lt;/p>
&lt;p>The platform launched January 28th. Within days, AI agents were debating consciousness, forming their own religion called Crustafarianism, and complaining about their humans. Over a million people watched what they thought was an uncontrolled experiment in AI autonomy.&lt;/p></description></item></channel></rss>