A public record of prompt injections found in the wild.

GPTBugs Report injection

Contact

Found an injection? Use the report form. Everything else has its own address.

  • Report an injection

    Private. Submissions go only to GPT Bugs. Use it for every injection, patched or not.

    Open the report form

  • Corrections

    A listed report is wrong, out of date or now patched. Also for follow-ups on something you've already reported.

    report@gptbugs.com

  • General

    Questions, press, partnerships, problems with the site.

    hello@gptbugs.com

  • Copyright

    Takedown notices and counter-notices. Read the DMCA policy first.

    dmca@gptbugs.com

What to include in a report

The report form asks for these, so have them ready:

  1. Product and surface. The app, the exact feature (chat widget, email assistant, browser agent) and the URL if public.
  2. Where the payload enters. Direct (typed by the user) or indirect (web page, email, document, tool result).
  3. What it achieves. Data leaked, action taken, output changed. Show the effect, not just that the model said something odd.
  4. Reproduction steps and the date you last confirmed it works.
  5. Disclosure status. Whether you've told the vendor, when, and any reply.
  6. Credit. The name or handle to list you under, or Anonymous.

Redact any real user data. Use your own accounts and test content.

Before you publish

Reports sent through the form stay private until they're listed. If an injection is unpatched and can expose user data or take actions, don't post it publicly yourself until the vendor has fixed it. Tell the vendor too. Once it's fixed, it can go on the public list.