Cursor updates spark security alerts, memory leak, and commit co-authoring
Community reports indicate recent Cursor updates introduced security alerts, memory leaks, and unexpected commit metadata behavior, prompting some teams to favor alternatives like Claude Code. Multiple users report a Cursor update triggering Microsoft Defender malware alerts, a <cursor_commands> memory leak, and unwanted 'Co-authored-by: Cursor' lines in Git commits ([Defender alert thread](https://forum.cursor.com/t/microsoft-defender-detects-cursor-update-as-trojan-win32-wacatac-b-ml-and-trojan-script-wacatac/151306)[^1], [memory leak report](https://forum.cursor.com/t/cursor-commands-memory-leak/151286)[^2], [commit co-author complaint](https://www.reddit.com/r/cursor/comments/1r05m6l/cursor_is_signing_commit_messages_now/)[^3]). A comparative review favors Claude Code for daily work and notes Cursor’s strengths but flags stability and pricing concerns ([tool comparison](https://www.reddit.com/r/ClaudeCode/comments/1qzkwav/i_spent_the_last_month_rotating_between_windsurf/)[^4], [Cursor rules regression](https://forum.cursor.com/t/cursor-rules-not-working-anymore/151255)[^5]). [^1]: Adds: community report of Defender flagging a recent Cursor update as Trojan. [^2]: Adds: user-reported memory leak in <cursor_commands> after update. [^3]: Adds: complaint about Cursor auto-adding 'Co-authored-by' lines in Git commits. [^4]: Adds: hands-on comparison praising Claude Code and outlining Cursor pros/cons. [^5]: Adds: report that Cursor Rules stopped working after an update.