Vercel breach weh connect to AI OAuth compromise show non-sensitive env vars

Vercel don reveal say dem suffer breach wey start from one worker account wey hackers take compromise — the account connect to third-party AI tool wey dey use Google Workspace OAuth. Vercel talk say the attackers later waka enter dia internal systems. New details show say customer environment variables still dey encrypted while dem dey rest if dem mark am as “sensitive.” But report from the Vercel breach say attackers fit access the “non-sensitive” variables, and that fit cause wahala if developers by mistake store API keys, RPC endpoints, or credentials without the correct sensitivity flag. Vercel never confirm for dia own say the claims wey dey for underground market (like internal credentials, source code, or staff records) true, and dem never confirm say dem tamper with live customer deployments. External experts (including Mandiant) and Context.ai dey involved to trace where am start from. For crypto traders, the main thing na operational security: plenty Web3 teams dey host frontends (dashboards, wallets, app UIs) for Vercel. If build artifacts or integrated services don change, users fit face higher risk of exposed endpoints or phishing-style attempts to drain wallets. Still, e no likely say e go change protocol fundamentals directly, so market impact go mainly come from sentiment for short term.