OptyStack LogoOptyStack Logo
Product
Features
Cost OptimizationCut SaaS waste with discovery, usage-backed rightsizing, and renewal leverage—often up to ~30% savings.Shadow IT DiscoveryDiscover unsanctioned SaaS, shadow AI, and unmanaged subscriptions in one place.License ManagementFind unused seats, eliminate zombie accounts, and automate renewals with usage-backed data.Contract Renewal TrackingOne renewal calendar with notice windows, usage context, and negotiation-ready briefs.Seamless App IntegrationsConnect Microsoft 365, Google Workspace, SSO, and 100+ SaaS brands into one live inventory.Identity Management with Zero Trust SecuritySingle sign-on and conditional access by IP, device, and region for your SaaS apps.
ROI Calculator
Resources

Support

  • Support
  • Knowledge Base
  • SaaS Directory
  • Partners

Content

  • SaaS Inflation Index
  • 2026 SaaS Audit Toolkit
  • Blogs
  • Success Stories
  • Events
PricingAboutContact
Start Free Trial
Book Demo
← All postsSaaS Governance

Agent Traces Are a Credential Store: What the Cursor Breach Teaches About Identity Risk

Ravi Singh · November 16, 2026

3D cybersecurity infographic illustrating identity risks associated with the Cursor breach, featuring a laptop displaying AI agent traces, API keys, access tokens, and session data, alongside a red security alert, locked credential folder, and protection shield.
Share
LinkedInX

Cursor’s November 2026 incident update shows how a key issued to a vendor led to exposed agent traces, then to access in SaaS tools, then to a malicious extension. The credentials never passed through a human sign-in. This guide walks through the chain and gives a five-point non-human identity checklist.

When a coding agent works on your systems, it sees your secrets. Every log, trace, or transcript of that work can hold them too. Cursor’s November 13, 2026 incident update shows how far that fact can reach. A key issued to a vendor led to exposed agent traces, then to access in Cursor’s SaaS tools, then to malicious copies of an extension. None of the later steps needed a person to sign in.

Last week’s post on the Notion and Fireworks breach covered fourth-party AI vendor risk, meaning the company behind your vendor. This post follows the credentials that move between those companies, and what they can open.

Related reading

Explore related guides and continue your SaaS optimization research:

  • Cross-Tenant Sync Offboarding: What Microsoft’s Known Issues Mean for Your Checklist
  • Your AI Vendor’s AI Vendor: What the Fireworks-Notion Breach Teaches About Shadow AI Sub-processors
  • BluePhishing: Why AI Agent Consent Is the New OAuth Blind Spot (and 7 Checks for Your Entra Tenant)
  • Your Vendor’s App Is an Identity Too: 5 Lessons from the MSP Process Breach

The Chain in Five Steps

Cursor’s account describes five steps.

1. A key was issued to a vendor. Cursor says it issued an access key to Fireworks, its AI infrastructure provider, and that the key was exposed. The attacker used it to copy data from a read-only storage bucket that Cursor had used to share data with Fireworks.

2. The vendor exposed it, and the bucket held traces. The bucket contained coding agent traces, mostly from 2025, from sessions that were not in Privacy Mode. Cursor says some traces contained credentials that had not been redacted. It puts the exposure at fewer than 0.01% of customers with API credentials compromised, and fewer than 0.05% of users outside Privacy Mode with traces exposed.

3. Agent traces leaked credentials. An agent that acts on infrastructure has to read the secrets it uses. Anything that records the agent’s work can capture those secrets too. The traces were a record of the work, and the secrets were inside it.

4. The credentials opened SaaS tools, then data. Cursor says the attacker used the exposed credentials to reach select SaaS tools. From those tools, the attacker accessed archived non-production source code repositories, some containing business contact information, along with limited customer support data and email conversations, product usage metrics and contact details, summaries of some coding agent conversations, and credentials that users had sent to Cursor’s support team.

5. A malicious extension followed. On October 29, Cursor says the attacker used a stolen credential from the exposed internal data to place malicious copies of Anthropic’s Claude Code extension on the cache that serves Cursor’s VS Code extension marketplace. Cursor says Anthropic did not publish the copies and that the flaw was not in Anthropic’s product. It says at most 5,000 users who requested specific cached versions that day may have received the build, which was available for about 11 hours. Cursor identified tampered versions 2.1.312 and 2.1.313. It also says that uninstalling the extension alone may not be enough.

Cursor says the last attacker activity it saw was on November 1, and that it was blocked.

Why MFA and SSO Were Not in the Path

The attack, as Cursor describes it, moved through keys and stored credentials. The first step was a key, and the later steps used credentials found in traces and storage. None of those steps required a user to sign in, so the controls designed for user sign-in did not apply.

Multi-factor authentication and single sign-on protect people who log in. They do not check whether a service accepts a key, whether an integration holds a valid token, or whether a storage bucket was shared with a partner. The same gap appeared in the MSP Process breach, where app credentials reached customer tenants without a user sign-in. In both cases, controls designed for people were not in the path.

That is why identity risk now has to cover non-human identities: the keys, grants, and agents that act without a person present.

Three Blind Spots

Credentials you have handed to vendors. A key issued to a vendor lives outside your environment. You may not know which vendor holds it, how long it lasts, or who inside the vendor can reach it. Cursor’s account shows that a key given to one vendor can become a route into another company’s systems.

Secrets in AI and agent logs. Traces, transcripts, and debugging logs can hold every credential an agent touched. Privacy modes, retention settings, and redaction decide how much of that survives. Cursor says some credentials were not redacted. A redaction process that misses one key is not a control to rely on alone.

OAuth and API grants into SaaS apps. An OAuth grant or API key gives an app standing access to your data. It keeps working after the person who approved it leaves, and it can be used from anywhere the token travels. In Cursor’s case, the attacker reached SaaS tools through credentials, not through a login.

A Five-Point Non-Human Identity Checklist

1. Inventory non-human identities and grants for each vendor. For every vendor, list the keys you issued, the OAuth grants and API connections it holds, and the agents or integrations it runs against your systems. Ask vendors which of their own suppliers hold those credentials, and record the scope of each one.

2. Set an owner and an expiry for each. Every key, grant, and agent needs a named owner who approves it and answers for its use, and an expiry date that forces review. A credential without an owner or an expiry is a standing risk.

3. Flag stale and unused tokens. Review last-used dates each month. Revoke tokens unused for 60 to 90 days, and treat tokens tied to departed employees or ended projects as stale on the day the owner leaves.

4. Be able to revoke everything for one vendor in one action. When a vendor reports a breach, you need to cut off every credential that vendor holds without searching across systems. Test the process on a non-critical vendor and time it. If it takes days, it is not yet a control.

5. Restrict integration access by network. Where a service supports it, limit integration and API access by IP address, device, or region, so a credential used from an unfamiliar network is denied. Cursor says it expanded network access restrictions for its own service providers, which is the same principle. Network restrictions will not stop a key that is already in an attacker’s hands on an allowed network, so pair them with rotation and expiry.

Cursor’s response also shows what to do after a breach. It deactivated the vendor’s key, rotated every exposed credential and, as a precaution, every credential in use internally, added secret scanning across its repositories, and redeployed production services. Those steps belong on your incident runbook, because they are the ones that end an incident.

Where OptyStack Fits

OptyStack covers the discovery and access visibility parts of this checklist. It finds SaaS and AI tools using signals from spend, SSO, and browser activity, and it maps each tool to the people who sign in to it. That gives you a starting inventory of the apps and AI tools connected to your business, with an owner assigned wherever one can be identified.

For access, OptyStack acts as the identity provider for connected third-party apps, according to its identity management page. It applies IP address, device, and region conditions to sign-ins for those apps and denies sign-ins that fail them.

OptyStack does not manage the keys a vendor holds, scan agent traces for secrets, or revoke every credential for one vendor in a single action. Confirm those capabilities in a demo before you rely on them. The inventory and owner steps are where OptyStack helps most. Rotation and revocation remain the work of your engineering and security teams.

To see the apps and AI tools connected to your business, you can start a free trial.

Unlock visibility. Slash SaaS waste.

Get real-time SaaS spend insights, discovery, and optimization in OptyStack Hub—start free, no credit card required.

Sign up for OptyStack Hub
PreviousCross-Tenant Sync Offboarding: What Microsoft’s Known Issues Mean for Your Checklist

Related articles

  • Cross-Tenant Sync Offboarding: What Microsoft’s Known Issues Mean for Your Checklist
    SaaS Governance

    Cross-Tenant Sync Offboarding: What Microsoft’s Known Issues Mean for Your Checklist

    Cross-tenant sync removes only the users it provisions, and deletion behavior depends on a setting many admins miss. This guide explains Microsoft’s documented limits, adds a Microsoft 365 offboarding checklist, and covers the February 2027 SMS and voice MFA retirement to plan for now.

    Nov 13, 2026

  • Your AI Vendor’s AI Vendor: What the Fireworks-Notion Breach Teaches About Shadow AI Sub-processors
    SaaS Governance

    Your AI Vendor’s AI Vendor: What the Fireworks-Notion Breach Teaches About Shadow AI Sub-processors

    A breach at AI infrastructure provider Fireworks exposed some Notion AI chat transcripts, and Notion turned off its Insights feature. Notion says its zero data retention promise did not cover that feature. This guide explains the lesson for AI vendor risk and gives a five-step sub-processor inventory.

    Nov 13, 2026

  • BluePhishing: Why AI Agent Consent Is the New OAuth Blind Spot (and 7 Checks for Your Entra Tenant)
    SaaS Governance

    BluePhishing: Why AI Agent Consent Is the New OAuth Blind Spot (and 7 Checks for Your Entra Tenant)

    Proofpoint’s BluePhishing research shows that one consent to a malicious AI agent blueprint can create up to 250 agent identities in a Microsoft Entra tenant. Those identities skip the controls built for people. This guide explains the proof of concept and gives seven checks for your tenant.

    Nov 12, 2026

  • Your Vendor’s App Is an Identity Too: 5 Lessons from the MSP Process Breach
    SaaS Governance

    Your Vendor’s App Is an Identity Too: 5 Lessons from the MSP Process Breach

    Stolen app secrets from MSP Process reportedly reached customer Microsoft 365 tenants with no user sign-in and no MFA prompt. This guide explains why MFA and SSO did not help, and gives a five-step third-party app permissions audit covering scopes, owners, secrets, and alerts.

    Nov 11, 2026

  • Shadow AI Discovery: Browser vs Endpoint vs SSO/OAuth vs Spend Data
    SaaS Governance

    Shadow AI Discovery: Browser vs Endpoint vs SSO/OAuth vs Spend Data

    Shadow AI discovery tools start from different places: the browser, the endpoint, SSO and OAuth grants, or spend data. Each one catches something and misses something. This guide compares the four methods and shows how OptyStack combines SSO, OAuth, browser, and finance signals.

    Nov 10, 2026

Keep reading

More guides on SaaS visibility, spend, and governance—jump between topics without leaving the blog.

View all posts →
  • Torii Alternatives and Freshservice SaaS Management Compared
    SaaS Optimization

    Torii Alternatives and Freshservice SaaS Management Compared

    Freshworks has agreed to acquire Torii and extend Freshservice into SaaS and AI spend management. This guide compares Torii alternatives side by side and sets out what to ask vendors about roadmap, pricing, AI spend coverage, and India support.

  • What the AU Small Finance Bank Leak Teaches Indian Companies About Third-Party SaaS Risk
    Vendor Management

    What the AU Small Finance Bank Leak Teaches Indian Companies About Third-Party SaaS Risk

    The AU Small Finance Bank data leak investigation highlights the risks of relying on third-party SaaS platforms. Explore the November 2 disclosure, five essential security checks, and a practical 30-day plan to strengthen SaaS visibility, access controls and vendor risk management.

  • Stolen AI Keys Are the New Shadow AI Bill

    Stolen AI Keys Are the New Shadow AI Bill

    Stolen AI API keys can turn hidden security gaps into unexpected bills. Explore the October 2026 AI platform breaches and learn how to inventory AI tools, assign key ownership, monitor spending, and revoke exposed credentials before costs escalate.

  • How to Offboard an Employee's AI Agents: A Checklist for IT Teams
    Best Practices

    How to Offboard an Employee's AI Agents: A Checklist for IT Teams

    Employees leave, but the AI agents they created and connected can keep running with active credentials. This checklist helps IT teams find every agent, OAuth grant, and API key tied to a departing employee, reassign or retire it, revoke access, and reclaim unused licenses.

  • AI Security Checklist for Businesses: How to Assess AI Features in SaaS Tools
    Vendor Management

    AI Security Checklist for Businesses: How to Assess AI Features in SaaS Tools

    AI features are appearing inside the SaaS tools businesses already use. Before enabling them, review what data they can access, how vendors process information, which controls are available, and whether the feature introduces new costs or risks.

  • How to Track AI Spend Per User Across GitHub Copilot, Claude, and ChatGPT
    Cost Management

    How to Track AI Spend Per User Across GitHub Copilot, Claude, and ChatGPT

    Seat counts no longer explain every AI bill. GitHub Copilot, Claude, and ChatGPT offer different usage reports and spending controls. Learn how to combine vendor billing data, identity logs, and expense records into one per-user view.

Ask the smartest LLMs about OptyStack

ChatGPTGeminiClaudePerplexityGrokCopilot
OptyStack LogoOptyStack Logo

The complete SaaS spend visibility and optimization platform. Connect, analyze, and optimize your entire software stack.

Product

  • Features
  • Integrations
  • Pricing
  • API

SaaS Directory

  • Browse All Apps
  • Slack
  • Microsoft 365
  • Salesforce
  • Zoom
  • Zoho One

Features

  • Cost Optimization
  • Shadow IT Discovery
  • License Management
  • Contract Renewals
  • App Integrations
  • Identity & Zero Trust

Tools & Resources

  • ROI Calculator
  • Knowledge Base
  • SaaS Inflation Index
  • Compare Tools
  • Getting started with OptyStack

Company

  • About
  • Blog
  • Success Stories
  • Events
  • Careers
  • Contact
  • Review us on G2

Stay updated

Get the latest insights on SaaS optimization

© 2026 OptyStack. All Rights Reserved.

LegalPrivacy PolicyTerms of Service