<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api-Keys on CuraSec</title><link>https://curasec.metacog.co.kr/tags/api-keys/</link><description>Recent content in Api-Keys on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 01 Nov 2026 17:05:59 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/api-keys/index.xml" rel="self" type="application/rss+xml"/><item><title>Northflank breach exposes customers' AI API keys</title><link>https://curasec.metacog.co.kr/insights/2026-11-01-northflank-security-breach-leads-to-abuse-of-customers-ai-ap/</link><pubDate>Sun, 01 Nov 2026 17:05:59 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-11-01-northflank-security-breach-leads-to-abuse-of-customers-ai-ap/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> If your org hosts workloads on Northflank, immediately rotate every secret and API key stored there and audit recent AI API usage for unauthorized spend or data exfiltration.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> If Northflank is in your environment, hunt for anomalous AI API activity (unexpected billing spikes, unusual query sources) since the breach window to identify any keys still being abused.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> Confirm whether your org uses Northflank; if so, request their formal incident report, assess the scope of exposed credentials, and direct teams to rotate affected secrets this week.&lt;/li>
&lt;/ul></description></item></channel></rss>