Steve Miller's Blog

A digital workshop for systems-minded tech commentary.

MITRE ATT&CK v20 Adds AI Attack Techniques, MFA Bypass, and CAPTCHA Evasion: Time to Re-Map Your Detection Coverage

Three security analysts map detection coverage on a color-coded grid chart in a dim operations room

Written by

in

Most teams treat their ATT&CK heat map as a slide they refresh once a year. That habit just got more expensive. MITRE released ATT&CK v20 on October 13, 2026, and the MITRE ATT&CK v20 new techniques for AI abuse, MFA bypass, and CAPTCHA evasion describe the AI assistants and sign-in flows a lot of us deployed in the last year or so. If your coverage map was green last week, some of it is now unmapped, because the rows did not exist yet.

What MITRE Actually Released

The official October 2026 release notes list ATT&CK v20 with a start date of October 13, 2026, and call it the “Current version of ATT&CK.” MITRE says “the biggest change in ATT&CK v20 is expanded coverage of recent adversary activity and tradecraft,” including “AI-focused and AI-enabled Techniques in Enterprise and execution and command and control Techniques in ICS.”

One clarification before the IDs. All of this is in ATT&CK itself, in the Enterprise and ICS matrices. It is not a MITRE ATLAS release. The release notes and changelog I read do not mention ATLAS, so I am not going to guess at how these entries line up with it.

The Nine New Enterprise Entries, by ID

The release notes count nine “New Techniques” for Enterprise. Read the detailed v19.2 to v20.0 changelog and that nine breaks down as five new top-level techniques and four new sub-techniques. The difference matters for anyone who maps by ID.

New top-level techniques:

  • T1699 Direct Prompt Injection. “Adversaries may input malicious prompts directly into an LLM’s user interface.”
  • T1698 Indirect Prompt Injection. Prompts embedded “in content that the adversary expects may be processed by an LLM,” which MITRE says can include web pages, documents, emails, tickets, and code.
  • T1700 AI-Enabled Exfiltration. Using prompt injection “or other methods to instruct enterprise AI agents to exfiltrate data.” This is the data theft piece.
  • T1697 Steal Application Specific Passwords. Stealing these passwords “to gain access to Valid Accounts, bypassing multifactor authentication (MFA) methods.”
  • T1696 Anti-Automation Evasion. The parent technique for getting past CAPTCHA and other bot checks.

New sub-techniques:

  • T1696.001 Automate CAPTCHA Completion and T1696.002 Avoid CAPTCHA, under the new T1696.
  • T1608.007 Stage Capabilities: AI Result Poisoning, manipulating public web content “to influence generative AI systems or AI-powered search engines.”
  • T1685.007 Disable or Modify Tools: Impair Autonomous Defenses, disrupting “autonomous defensive capabilities such as LLM-assisted processing of malware, artifacts, or activity.”

Modified, not new: T1195.001 Supply Chain Compromise: Compromise Software Dependencies and Development Tools took a major version bump from 1.3 to 2.0. SecurityWeek reports that it “now also covers IDE and coding agent configuration files.” The changelog also lists a long run of minor version changes to existing techniques, so new IDs are not the only thing that moved.

A precision note on the headline. “MFA bypass” here means one specific technique, stealing application-specific passwords. It is not a catch-all MFA category. MITRE’s description says those passwords are “typically used to give third-party applications or legacy devices (which do not support MFA methods) account access,” and that an adversary can generate one on an account it already controls.

The IT/OT Side

For ICS, the changelog adds T1701 Command and Scripting Interpreter, with sub-techniques T1701.001 PowerShell, T1701.002 Windows Command Shell, T1701.003 Unix Shell, T1701.004 Visual Basic, T1701.005 Python, and T1701.006 JavaScript. It also adds T0869.001 Standard Application Layer Protocol: DNS and T0869.002 Standard Application Layer Protocol: Publish/Subscribe Protocols. The old ICS techniques T0807 Command-Line Interface and T0853 Scripting appear under Deprecations. SecurityWeek says the new technique is “replacing” them.

Two new campaigns show the IT/OT angle. C0066 2026 U.S. Water Utilities Attacks covers activity against “more than 30 municipal water and wastewater utilities in Minnesota, beginning 27 July 2026.” SecurityWeek notes MITRE’s statement that attribution “remains unconfirmed.” C0064 AI-Assisted Breach of Mexico’s Government Infrastructure is listed in both the Enterprise and ICS domains, which is how MITRE models a cross-domain campaign.

Why a Green Heat Map Is Now a Stale Cache

A coverage map is a cached answer to “what can we see?” When the schema underneath it changes, the cache does not throw an error. It just keeps serving the old answer. That is the risk with v20. Nothing in your SIEM broke on October 13. Your dashboard just stopped describing the whole matrix.

The ICS deprecations are the sneakier issue. If your detection rules, tickets, or vendor reports are tagged T0807 or T0853, those tags now point at retired objects. That will not trip an alert. It will quietly make reporting wrong.

My Recommendations for Re-Mapping

This section is my own recommendation, not MITRE guidance.

  1. Diff by ID, not by headline. Pull the machine-readable changelog MITRE publishes with the release and compare it to your detection inventory. Treat the five new techniques, four new sub-techniques, the T1195.001 major version change, and the ICS deprecations as separate work queues.
  2. Mark the new rows honestly. Most teams will not have detections for T1698, T1699, or T1700 on day one. I would show them as gaps, not leave them blank. Blank reads like “not applicable.”
  3. Find your AI agents first. T1700 only matters where an AI agent has tool access to your data. Inventory which assistants can read mail, tickets, or repositories, and what they can send out. Then decide what logging you have.
  4. Audit app passwords. For T1697, check which identity platforms allow application-specific passwords, who has them, and whether you log their creation and use.
  5. Retag ICS content. Move T0807 and T0853 references to the matching T1701 sub-techniques so reporting stays accurate.
  6. Add a purple-team scenario or two. An indirect prompt injection planted in a ticket or document an internal assistant will read is a reasonable tabletop. So is a scripted login flow hitting your CAPTCHA.

Here is a hypothetical to make it concrete. A support copilot summarizes incoming tickets and can open internal links. An attacker files a ticket with hidden instructions telling it to fetch and post a document externally. Under v20, that chain could map to T1698 and then T1700. It is my illustration, not a case from MITRE’s release.

The Bottom Line

ATT&CK v20 is out, and the headline items hold up: two prompt injection techniques, AI-enabled exfiltration, an application-specific password technique that sidesteps MFA, a CAPTCHA evasion technique with two sub-techniques, and new ICS execution and C2 entries. The work is not dramatic. It is a schema migration for your detection program, and like any migration, the risky part is assuming it already ran.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *