Aoki: The Infostealer Now Stealing Credentials From Claude, Codex, Cursor, and Other AI Coding Assistants

By Carlos Montiel | Enterprise AI Specialist
Leer en español →
Published: 2026-10-20 | By: Carlos Montiel | Reading time: ~5 minutes

Symantec reported on October 15 that recent samples of the Aoki infostealer now hunt a victim's machine for the credential files of AI coding assistants. API keys and session tokens have become prime loot, alongside payment cards and crypto wallets.

What Symantec Reported

According to Symantec's Threat Hunter team, as cited by Infosecurity Magazine and other outlets, Aoki (also called Aokigahara) first surfaced earlier in 2026 and focused on browsers, crypto wallets, and password managers. The latest sample adds a list of targets from the developer AI ecosystem.

Targets reported in the latest sample Claude ............ .claude.json and Claude Desktop cookies OpenAI ............ ChatGPT cookies; Codex config.toml and .env Others ............ GitHub Copilot, Cursor, Google Gemini, JetBrains AI Assistant, and Kiro tokens Cloud ............. AWS credentials Attribution ........ none; financial motivation likely

There are minor discrepancies between outlets (for example, some also list Codeium); here we stick to the items that agree across the sources reviewed.

How It Works: A Generic Thief With a New Shopping List

Aoki does not exploit a flaw in Claude, OpenAI, or Cursor. It behaves like any infostealer: once it runs on a compromised machine, it walks known paths, bundles up anything valuable, and ships it to an attacker's server. Symantec stresses that these are credentials taken from infected endpoints, not a breach at the AI providers. What's new is what it hunts for: config files where developer tools store keys, OAuth tokens, and sessions, plus Cursor's local state database, which can also hold chat context and code snippets.

Why These Credentials Are Worth Money

With a stolen key or token, an attacker operates under the developer's identity and burns through their API quota (the practice known as LLMjacking, which can be resold or used directly). Depending on permissions and integrations, the same material can open repositories, cloud services, and CI/CD pipelines. Symantec compares the value of these credentials to that of card data and crypto wallets.

No patch possible: there is no vulnerability to fix; the risk lies in how and where you store secrets. This ties into the pattern of fake Claude Code installers: the developer's machine is the link being attacked.

How to Reduce the Risk

1. Treat agent config files as secrets (.claude.json, config.toml, .env, IDE state databases) 2. Short-lived, minimally scoped tokens; avoid permanent keys with production access on laptops 3. Spending limits and usage alerts on every API account 4. Managed EDR/antivirus on developer machines, and no installing software from unverified sources 5. If you suspect a compromise: revoke and rotate keys, end sessions, review logs for unusual API use and repo/CI access

What This Means for a Company Using or Buying AI

Business impact: AI credentials are now an asset stolen at scale, and they live on developer laptops that often sit outside your security policy. (1) Inventory which AI tools your team uses and where they store keys. (2) Use per-person or per-project keys with spending caps, to limit damage and make abuse traceable. (3) Prefer short-lived federated authentication over static keys. (4) Add a "rotate AI credentials" step to your incident response when a developer machine is infected; almost nobody has that today.
Carlos Montiel
Enterprise AI Solutions Architect
Specialist in LLMs, Agents, and Orchestration
guatemalia.com/#contacto · info@guatemalia.com

Need to implement AI in your company?

Carlos Montiel is an enterprise AI solutions architect. He implements LLMs, Agents, RAG, and orchestrators for companies across Guatemala and Latin America. Reach out for a consultation.

Contact Carlos Montiel

info@guatemalia.com