<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Saas-Breach on CuraSec</title><link>https://curasec.metacog.co.kr/tags/saas-breach/</link><description>Recent content in Saas-Breach on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 14 Jul 2026 12:08:08 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/saas-breach/index.xml" rel="self" type="application/rss+xml"/><item><title>Vercel confirms April 2026 breach; stolen data reportedly for sale</title><link>https://curasec.metacog.co.kr/insights/2026-07-14-vercel-april-2026-security-incident/</link><pubDate>Tue, 14 Jul 2026 12:08:08 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-14-vercel-april-2026-security-incident/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Vercel stores environment variables, API keys, and deployment tokens — rotate all Vercel personal/team API tokens and audit env-var secrets stored on the platform immediately; check for unauthorized deploys or repo access in your Vercel audit logs.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> If your estate uses Vercel, hunt for suspicious CI/CD activity or deployments since April 2026 using potentially stolen credentials; monitor for attacker re-use of Vercel tokens in downstream cloud accounts.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> Confirm whether your organization has Vercel accounts, then request Vercel&amp;rsquo;s incident scope and attestation this week; brief engineering leadership on potential exposure of source code, build secrets, or customer-data-touching environment variables before this reaches the news cycle internally.&lt;/li>
&lt;/ul></description></item></channel></rss>