AntiFox AI: AWS credential theft

AWS

AntiFox AI targets AWS credentials using agentic AI, exploiting exposed credentials

Do this now

Check AWS's advisory for a fix and rotate any exposed AWS credentials now.

Who should check: teams running AWS

First seen: 11 Nov 2026
Last update: 11 Nov 2026, 19:18 UTC
Source: news
On the menu as: AWS

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## AntiFox AI: AWS credential theft
Severity: unknown. Patch status: fix status unknown.
Affected: AWS

AntiFox AI targets AWS credentials using agentic AI, exploiting exposed credentials

## Steps
1. This incident involves a provider (aws). Search config, CI and env templates (.env.example, wrangler.toml, vercel.json, terraform, workflow secrets) for credentials stored there. List each secret by name, where it is used, and how to rotate it. Never print secret values.
2. No source names a fix yet; check the vendor advisory. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://blog.gitguardian.com/another-new-ai-hacking-agent-vs-the-same-credential-problem-antifox-targeting-aws-credentials/
https://pwned.coffee/i/antifox-ai-aws-credential-theft-2

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 13 Nov 2026, 16:26 UTC

Sources: KEV – CVE record – Vendor –

Sources

blog.gitguardian.com: AntiFox Targeting AWS Credentials: The Latest Wave of AI Agent Attacks

Follow on X

Totalone coffee