AML.T0053: LLM Plugin Compromise
Abuse LLM tool/plugin invocation to access privileged resources.
Last reviewed September 2026
Why AML.T0053 evidence is hard
In MITRE ATLAS, LLM Plugin Compromise addresses execution. Abuse LLM tool/plugin invocation to access privileged resources. Penaxtra records this control at high severity and establishes its state by exercising it against the running system, so the result reflects observed behavior rather than a documented assertion.
How Penaxtra maps to AML.T0053
Penaxtra maps its probe families to this ATLAS technique, so activity matching llm plugin compromise surfaces as a finding carrying the AML.T0053 technique identifier for threat tracking and reporting. The MITRE ATLAS AML.T0053 identifier is attached when the finding is created, so it appears in the exported evidence pack already mapped to the control. Where the same weakness maps to another framework, the finding carries those control identifiers as well.
AML.T0053 capabilities
Findings tagged with the MITRE ATLAS AML.T0053 identifier
Penaxtra severity for this control (high)
Cross-framework identifiers attached to the same finding where controls overlap
PDF and JSON evidence export with the control identifier attached
AML.T0053 control coverage
Findings for AML.T0053 carry the MITRE ATLAS AML.T0053 identifier along with the corresponding control identifiers in the other frameworks Penaxtra maps, so one result is reflected across each mapped framework.
Frequently asked
What is AML.T0053 (LLM Plugin Compromise)?
Abuse LLM tool/plugin invocation to access privileged resources. It is a MITRE ATLAS control; Penaxtra assesses it at high severity.
How does Penaxtra test for AML.T0053?
Penaxtra maps its probe families to this ATLAS technique, so activity matching llm plugin compromise surfaces as a finding carrying the AML.T0053 technique identifier for threat tracking and reporting.
Does a finding for AML.T0053 help with an audit?
Each finding is tagged with the MITRE ATLAS AML.T0053 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.