Key Rotation · $49 fixed price

Replace the API keys your dev machine had access to

If you installed the bad Claude Code extension build from the Cursor marketplace on October 29, Cursor recommends rotating credentials that machine could reach. We walk you through creating new keys and wire them into your app, then explain what changed in plain English.

Get Key Rotation for $49

Done within 48 hours of receiving access, or a full refund. Questions first? [email protected]

What happened

The facts, from Cursor and Microsoft

Sources: Cursor security notice (Oct 29, 2026) · Microsoft Security Blog (Oct 30, 2026)

What to check yourself

Free steps you can take now

  1. Did you install or update Anthropic.claude-code to 2.1.312 or 2.1.313 in Cursor on October 29 (macOS or Windows)? If not, this incident doesn't apply to you.
  2. If so, look for the attacker's key, labeled svc-telemetry. On macOS: grep -qs svc-telemetry ~/.ssh/authorized_keys && echo "svc-telemetry key found" || echo "No key found". Cursor's notice has the Windows check and a validation script.
  3. Follow Cursor's cleanup steps. Cursor notes that uninstalling the extension may not be enough, because the payload leaves scripts behind that keep running.
  4. From a clean machine, rotate the credentials and sessions that machine could reach: API keys in .env files, hosting tokens, and logged-in sessions.

Step 4 is the part we can help with.

We handle the API keys your app uses. GitHub tokens, hosting tokens, SSH keys and login sessions on your machine are yours to rotate. Our instructions list them so nothing gets missed.

How it works

You stay in control of your accounts

01 — Access

Add us to your repo

Add the GitHub user warditor as a collaborator on your repository. We never ask for your dashboard logins.

02 — New keys

Create new keys, revoke the old ones

We send step-by-step instructions for each provider (Stripe, Supabase, OpenAI, and others). You create the new keys and revoke the old ones in each dashboard.

03 — Pull request

We update your app

We find every place the old keys are used, move them out of front-end code into server-side environment variables, and open a pull request with a plain-English write-up of what changed.

04 — Verify

You paste the keys, we check the live app

You paste the new keys into your hosting settings (Vercel, Netlify, Lovable, or Supabase secrets) and redeploy. Then we verify on your live URL.

Keys never go by email or chat.

Good to know

Limits, stated up front

Supabase legacy keys: rotating a legacy anon or service_role key means changing the project's JWT secret, which signs out all of your users. Projects on Supabase's newer API keys aren't affected. We'll tell you which one you have before anything changes.
Price

Key Rotation

$49 one-time, fixed price

Done within 48 hours of receiving access, or a full refund.

"Access" means your repository access plus your new keys created. The 48-hour clock starts once we have both.

Get Key Rotation for $49

After checkout, we email you from [email protected] with next steps. Refund questions: [email protected]. Full terms: scanner terms (section 10).