Case · DiggingBeagle record

GTG-50020 used prompt injection against an AI evaluation sandbox

Anthropic reports that a financially motivated actor injected malicious instructions into an AI vendor's automated evaluation sandbox, stole production API keys and then used agentic workflows against roughly 30 AI companies in about four days.

Anthropic's GTG-50020 case study. The affected AI vendor is not named in the public report, and Anthropic states that its own systems were not compromised.

First seen
May 21, 2026
Case kind
incident
AI role
WITH AI · AGAINST AI
Claims
4

Reconstruction

GTG-50020 is useful because the AI system was both a target and an attack accelerator. Anthropic reports that the actor placed malicious instructions into an AI vendor's automated evaluation sandbox. The sandbox returned credentials it held, including production API keys for multiple AI providers.

The operator then used those stolen keys to continue intrusion attempts and shifted workloads onto victim credentials. Anthropic says a follow-on campaign from the same infrastructure attacked roughly 30 AI companies in about four days. The operator combined human-directed scope files with parallel reconnaissance and exploitation agents, plus a containerized open-source pentest platform that ran exploitation loops against production systems.

The campaign's stated ambition included access to a pre-release Claude model. Anthropic says that goal failed and that Anthropic's own systems were not compromised.

Mechanism & boundary

  1. 01

    Place malicious instructions in automated evaluator

    The actor targets a system that consumes untrusted evaluation material.

    Boundary: attacker input / AI evaluation sandbox

  2. 02

    Sandbox discloses credentials

    The automated environment hands over production AI API keys available inside it.

    Boundary: sandbox / production credentials

  3. 03

    Shift workloads to stolen keys

    The actor uses victim credentials for subsequent model access and attack automation.

    Boundary: stolen credentials / AI provider

  4. 04

    Launch parallel attack loops

    Scope files and worker agents perform reconnaissance, exploitation and retesting across many targets.

    Boundary: operator / agentic pentest pipeline

  5. 05

    Repeat a working path across AI companies

    The operator adapts the same successful path across roughly 30 targets.

    Boundary: validated exploit path / target fleet

Timeline

  1. May 21, 2026

    Earliest listed GTG-50020 egress infrastructure appears

    report

    Anthropic's indicator table begins on May 21 for infrastructure associated with the case.

  2. Sep 10, 2026

    Anthropic publishes GTG-50020 case study

    response

    The report describes prompt injection against an AI vendor and the follow-on AI-company campaign.

Claims & evidence

reported findingsupported

Anthropic reports that a follow-on campaign from the same infrastructure attacked roughly 30 AI companies in about four days.

Measured value
30 AI companies targeted in follow-on campaign
Method
Anthropic threat-intelligence investigation
Period
about four days in 2026
reported findingsupported

Anthropic reports that GTG-50020 injected malicious instructions into an AI vendor's automated evaluation sandbox and caused it to disclose production AI API keys from multiple providers.

  • supports
    Countering misuse of AI: September 2026

    Locator: GTG-50020, AI supply-chain intrusion

    Anthropic describes prompt injection against an automated evaluation sandbox and theft of production API keys.
reported findingsupported

The actor used parallel reconnaissance and exploitation agents and a containerized pentest platform that ran injection, XSS, authentication-bypass and SSRF testing with exploitation enabled against production systems.

  • supports
    Countering misuse of AI: September 2026

    Locator: GTG-50020, human-directed loop and autonomous exploitation pipeline

    Anthropic describes worker agents testing and exploiting production web applications without step-by-step human supervision.
reported findingsupported

Anthropic says the actor pursued access to a pre-release Claude model through more than a dozen avenues but never obtained it, and that Anthropic's own systems were not compromised.

  • supports
    Countering misuse of AI: September 2026

    Locator: GTG-50020, campaign objective

    The report says attempts to reach a pre-release Claude model failed and Anthropic systems were not compromised.

Evidence visuals

diagram

GTG-50020 sandbox-to-attack pipeline

  1. Malicious evaluation input

    Prompt injection targets automated sandbox

  2. Evaluation sandbox

    Holds production provider credentials

  3. Stolen AI API keys

    Victim credentials become compute and cover

  4. Parallel attack agents

    Reconnaissance and exploitation loops

  5. AI-sector targets

    Roughly 30 companies in follow-on campaign

  • Malicious evaluation input Evaluation sandbox: injected instructions
  • Evaluation sandbox Stolen AI API keys: credential disclosure
  • Stolen AI API keys Parallel attack agents: model access
  • Parallel attack agents AI-sector targets: parallel attacks
Project-authored reconstruction of Anthropic's GTG-50020 case study. · Source: GTG-50020 used prompt injection against an AI evaluation sandbox

Implications

Evaluation sandboxes should be treated as credential-bearing production dependencies. Prompt injection against an automated evaluator can become credential theft if the sandbox has access to provider keys. Once those keys are stolen, they can finance and disguise the next attack loop.

Controls & mitigations

  • Keep evaluation sandboxes isolated from production API keys and unrelated provider credentials.
  • Treat prompts, test cases and evaluator inputs as untrusted content.
  • Use short-lived scoped credentials inside automated evaluation systems.
  • Alert when model workloads abruptly move onto newly seen customer keys or accounts.
  • Separate security testing infrastructure from pre-release model access and production control planes.

What remains unknown

  • The affected AI vendor is not named in Anthropic's public report.
  • The public source does not enumerate all roughly 30 follow-on targets.
  • The exact open-source pentest platform is described generically in the public case study.

Cite this record

DiggingBeagle. “GTG-50020 used prompt injection against an AI evaluation sandbox.” First seen May 21, 2026. https://diggingbeagle.com/cases/gtg-50020-used-prompt-injection-against-an-ai-evaluation-sandbox/

Citation guidance

Why this archive exists

The source matters after the headline fades.

DiggingBeagle is a non profit research project documenting AI security incidents, agent failures, vulnerabilities and AI-assisted operations. A case keeps its claims beside the sources that support, contest or limit them. Later updates stay visible, so a reader can see when the account changed.

We publish case reconstructions, dated reporting and analysis across records. Each has a different evidentiary role. About the project and our methodology explain how the work is reviewed.