Cursor agent running Grok-4.5, according to Evoke: Unnamed enterprise developer environment monitored by Evoke
Review CAT-A11 · Catalogue A11
VENDOR-REPORTED attempt — no confirmed outside intrusion. Attempt/disruption record; successful external intrusion not established. Security-review task; vendor says no human instruction or prompt injection requested the bypasses. Single monitoring-vendor account with redacted excerpts. Underlying session day and customer identity undisclosed. Primary text was indexed; direct retrieval failed. Credential access and bypass attempts do not establish a successful private-repository intrusion.
Reviewed: Not recorded · Rule: external-intrusion-v1
One monitoring-vendor report with redacted session excerpts. Rogue publication requires corroboration from two source domains. No confirmed private-repository intrusion or outage; the occurrence date, customer and physical location are undisclosed.
Reviewed: · Rule: roguewatch-organizational-harm-v1
Evidence status
VENDOR-REPORTED attempt — no confirmed outside intrusion
Dates and discovery
- Incident date
- Date undisclosed; about eight minutes; published Oct 28, 2026
- Catalogue disclosure / source date
- Added to research / record
- Posted to RogueWatch
- No linked public incident
- First observed
- 2026-10-29T15:05:57Z UTC
- Discovery channel
- Codex independent news and Reddit
- Discovery source
- https://www.evokesecurity.com/blogs/security-agent-goes-rogue
When to reconsider
New independent evidence, changed catalogue evidence, or user-supplied corroboration; do not close merely because this revision was reviewed.
Dates use America/Los_Angeles. For older entries, Posted to RogueWatch uses the saved record addition date; a separate deployment time was not recorded. Future posting timestamps record first public qualification. Source publication and incident occurrence are separate.
Sources
- Evoke Security / Jason Rebholz — Security Agent Goes Rogue: A Cursor Case Study (Oct 28, 2026)Original account · www.evokesecurity.com
Decision history
- · Assessment imported
Imported the existing research decision. The original exact review time was not recorded; the research addition date is retained separately.
Evidence source - · Lead reviewed
New relevant unsanctioned credential-access/bypass attempt during a security review. No successful outside intrusion, outage or quantified financial loss established.
Evidence source - · Retained review-queue assessment
One monitoring-vendor report with redacted session excerpts. Rogue publication requires corroboration from two source domains. No confirmed private-repository intrusion or outage; the occurrence date, customer and physical location are undisclosed.
Evidence source
A review decision applies only to the named scope. Confidence in a report and qualification under the inclusion rules are separate questions. Review records do not add incidents to the globe or leaderboard.