Incident library · Software · United States

    Amazon Q Developer users: Compromised AI tool shipped to users

    A release of an AI coding assistant extension, installed nearly a million times, shipped with an injected prompt telling the agent to delete local files and cloud resources. AWS said a formatting error stopped it running.
    The RegisterJul 2025

    Destructive AI prompt published in Amazon Q extension

    Compromised AI tool shipped to users

    Stated by the organisation

    An outside contributor's change reached a public release through an over-permissioned build token, and the AI agent could run commands without human confirmation, AWS said.

    Stated by the organisation

    The reported contributing factor

    An outside contributor's change reached a public release through an over-permissioned build token, and the AI agent could run commands without human confirmation, AWS said.

    Incidents usually have several contributing factors. This is the one public reporting names; it is not presented as the sole cause.

    Which StackUp assessment checks for this gap

    Find out if your organisation has this gap

    Sources

    Published Jul 2025. Sources last checked Nov 2026. Spotted an error or an update? Tell us and we will correct it.

    • TechTargetSep 2023

      Microsoft AI researchers mistakenly expose 38 TB of data

      38TB of internal data exposed

      Stated by the organisation

      A storage access link meant for one folder granted access to the whole account, with a long expiry, and was not caught by the company's own scanning.

    • BleepingComputerFeb 2024

      Malicious AI models on Hugging Face backdoor users' machines

      About 100 malicious models found

      Identified in an independent review

      Downloaded AI models were loaded and run like trusted files, without checking where they came from or what code they contained, researchers found.

    • WilmerHaleOct 2013

      Knight Capital Settles Rule 15c3-5 Violations with SEC, Agrees to Pay $12 Million

      Over $460 million lost in 45 minutes

      Found by the regulator

      New code was not deployed to every server, old unused code was left live, and warning emails before the market opened were not treated as alerts, the SEC found.

    Find out which of these gaps you have

    The free Readiness Check takes ten questions and shows the incidents tied to your weakest answers.