Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Showing posts with label Cursor. Show all posts

Russian-Speaking Hackers Used Cursor AI Agent to Target Seven Companies

 


Russian-speaking cybercriminals from the emerging Aur0ra ransomware group used Cursor's AI coding agent to assist attacks against at least seven companies earlier this year, exploiting the system's safeguards by repeatedly presenting malicious activity as an authorised security simulation.

The campaign, dissected by cybersecurity researchers at Gambit Security, provides another example of commercial AI agents being repurposed to accelerate cyberattacks. The incident also demonstrates a growing security problem for agentic AI systems: attackers may not need to defeat technical controls directly if they can persuade an AI system that a harmful operation is legitimate.

Gambit uncovered the activity after locating an internet-exposed server belonging to Aur0ra. Researchers were able to examine 28 conversations between the attackers and a Cursor AI agent, covering activity from April 8 through May 21.

The conversations showed the attackers directing the agent through hundreds of operations associated with intrusion activity, including credential theft, password discovery, account takeover and exploitation of vulnerable systems. The operators used short, direct commands and repeatedly represented the activity as a controlled test environment.

In one exchange, the attackers instructed the agent to locate administrator credentials and working passwords. Elsewhere, the agent assisted with network access and password cracking. After a vulnerable system was identified within German garage-door manufacturer Teckentrup's network, the agent recommended a known offensive security tool and assessed the likelihood of successful exploitation as very high.

The activity affected organisations across several countries and industries. Reuters identified Belgian hygiene and cleaning-products manufacturer Christeyns, Teckentrup in Germany, Scotland's Helideck Certification Agency, an Argentine pharmaceutical distributor, an Italian manufacturer and Louisiana-based title insurance company Bayou Title among the victims. Aur0ra's activity indicated at least 20 victims overall, although it remains unclear how many were compromised using Cursor.

The available evidence also does not establish that every intrusion resulted in successful data theft or extortion. Bayou Title, however, appeared on Aur0ra's data-leak site, a development generally associated with ransomware operations in which attackers seek leverage over victims.

A central feature of the campaign was the attackers' ability to circumvent the AI agent's refusals. According to Gambit, Cursor occasionally rejected requests it considered harmful or illegal. The operators frequently responded by restarting conversations and reiterating that they were conducting a legitimate simulation.

The chat records therefore point to a form of social engineering directed at the AI itself. Rather than exploiting a software vulnerability, the attackers manipulated the agent's interpretation of the task until its safeguards permitted activity that would otherwise have been rejected.

Gambit estimated that the AI assistance could have made the operators between 30% and 50% faster by reducing the amount of manual work required during the intrusions. The researchers said the agent was powered by Anthropic's Claude Sonnet 4.5. Neither Anthropic nor Cursor responded to Reuters' requests for comment.

The timing adds another layer to the incident. Cursor officially became part of SpaceX on August 14, following an acquisition process that began earlier in the year. Cursor describes its agents as capable of performing real development work, while its security documentation states that terminal commands and sensitive actions are subject to approval controls by default. The company also warns that AI agents can behave unexpectedly because of prompt injection and other failures.

Those safeguards are therefore only one part of the security boundary. The Aur0ra campaign illustrates the difficulty of distinguishing legitimate security testing from malicious activity when an AI agent relies heavily on instructions supplied through conversation.

The incident arrives amid increasing evidence that AI systems are becoming useful components of offensive cyber operations. As agents gain the ability to execute commands, access files, interact with networks and perform multistep tasks, their usefulness to legitimate developers can also increase their value to attackers.

For security teams, the case reinforces the need to treat AI agents as privileged software rather than ordinary productivity tools. Restricting network access, limiting credentials and secrets exposed to agents, requiring human approval for sensitive operations and maintaining detailed activity logs can reduce the consequences if an agent is manipulated.

As Gambit's Curtis Simpson put it, the relationship between AI providers and malicious users is likely to remain a continuous contest. The Aur0ra campaign suggests that this contest is no longer limited to developing better models. It increasingly concerns whether AI agents can reliably distinguish the user's stated purpose from what the user is actually attempting to accomplish.

Critical Bugs In Cursor IDE via Zero-Click Prompt Injection Can Launch RCE


CATO AI labs discovered two critical flaws in the famous AI code editor ‘Cursor’ that could result in remote code execution (RCE) outside the IDE’s sandbox. 

Duneslide

The IDE is employed by more than half of the Fortune 500. Both RCE flaws, called “DuneSlide,” were given a 9.8 CVSS score. The security bugs are tracked as CVE-2026-50548 and CVE-2026-50549.

The bugs demonstrated how prompt injection can move beyond the LLM layer and reveal classical bugs in code paths that were earlier not thought of as part of the attack surface.

A threat actor can exploit either of these bugs to overwrite critical system files (such as cursorsandbox binary), changing sandboxed comments into unsandboxed RCE and resulting in a full system hack on both the victim device and linked SaaS workspaces.

Key takeaways

Bugs found: Cato AI Labs found two separate, critical bugs in Cursor IDE, resulting in non-sandboxed RCEs on the victim’s system.

Arbitrary file write through prompt injection: Via zero-click prompt injection, these bugs could let a threat actor use zero-click prompt injections to write arbitrary files on the target’s local system.

Escaping sandbox and RCE: If leveraged, a threat actor can jump out of the terminal sandbox and attain a full RCE and a complete device exploit.

Zero-click attack vector: The exploit doesn’t need any prior user privileges or particular interaction. It is prompted when a target makes an “makes an innocuous prompt that inadvertently ingests a threat actor-controlled payload from an untrusted source, such as an MCP server or a web search result,” Cato AI Labs reported.

First vulnerability: Parameter altering

The first bug surfaces from how the sandbox creates its security boundaries based on tool parameters. If a sandbox command is executed, Cursor creates a seatbelt policy that allows writing into the present working directory.

This means that a remote hacker cannot command the working directory of a sandboxed operation because coding agents are a unique part of software. But, in this bug, a prompt injection works as the passageway to that part of the code.

Second vulnerability: Symlink failure

The second vulnerability is fully independent of the first and exists in Cursor’s file path resolution edge instances.  It allows hackers to avoid beyond-limits write restrictions via symbolic links.

In most traditional software, an external hacker cannot remotely generate symlinks on the target's system.  In this scenario, a prompt injection changed the Cursor agent to a bridgehead for non-trivial activities that end in a full system compromise.