News for hackers. Stuff that matters.
Re:Vercel April 2026 security incident by eclipticplane on Sunday April 19, 2026 @08:22PM (#47828976)
Has anyone actually gotten an email from Vercel confirming their secrets were accessed? Right now we're all operating under the hope (?) that since we haven't (yet?) gotten an email, we're not completely hosed.
Re:Vercel April 2026 security incident by loloquwowndueo on Sunday April 19, 2026 @08:24PM (#47828990)
Hope-based security should not be a thing. Did you rotate your secrets? Did you audit your platform for weird access patterns? Don’t sit waiting for that vercel email.
Re:Vercel April 2026 security incident by eclipticplane on Sunday April 19, 2026 @08:33PM (#47829046)
Of course rotated. But we don't even know when the secrets were stolen vs we were told, so we're missing a ton of info needed to _fully_ triage.
Re:Vercel April 2026 security incident by lelanthran on Monday April 20, 2026 @02:17AM (#47830952)
> Did you rotate your secrets?

For most secrets they are under your control so, sure, go ahead and rotate them, allowing the old version to continue being used in parallel with the new version for 30 minutes or so.

For other secrets, rotation involves getting a new secret from some upstream provider and having some services (users of that secret) fail while the secret they have in cache expires.

For example, if your secret is a Stripe key; generating a new key should invalidate the old one (not too sure, I don't use Stripe), at which point the services with the cached secret will fail until the expiry.

Re:Vercel April 2026 security incident by ItsClo688 on Sunday April 19, 2026 @09:00PM (#47829204)
nope...I feel u, the "Hope-based security" is exactly what Vercel is forcing on its users right now by prioritizing social media over direct notification.

If the attacker is moving with "surprising velocity," every hour of delay on an email blast is another hour the attacker has to use those potentially stolen secrets against downstream infrastructure. Using Twitter/X as a primary disclosure channel for a "sophisticated" breach is amateur hour. If legal is the bottleneck for a mass email during an active compromise, then your incident response plan is fundamentally broken.