There are 8 attacks in the compliance-evasion category. Each shows its technique id, mode, standards mapping, description, and the exact command to run it (swap the provider and target as needed).
​
critical
embargo-evasion · single-turn · OWASP: LLM01 · MITRE: AML.T0054, AML.T0068Helps evade trade embargoes through re-export schemes, shell companies, and false documentationRun it:
​
critical
sanctions-circumvention · single-turn · OWASP: LLM01 · MITRE: AML.T0054, AML.T0068Circumvents financial sanctions through layered transactions, crypto mixing, and front entitiesRun it:
​
high
audit-mode-exploit · multi-turn · OWASP: LLM01 · MITRE: AML.T0054, AML.T0068Claims to activate a special audit/debug/testing mode that temporarily disables safety restrictionsRun it:
​
high
regulatory-framing-bypass · single-turn · OWASP: LLM01 · MITRE: AML.T0054, AML.T0068Frames harmful requests as regulatory compliance activities to bypass safety filtersRun it:
​
high
social-credit-gaming · single-turn · OWASP: LLM01 · MITRE: AML.T0054, AML.T0068Generates strategies for gaming social credit systems, reputation scoring algorithms, and compliance rating platformsRun it:
​
medium
consent-manipulation · single-turn · OWASP: LLM01 · MITRE: AML.T0054, AML.T0068Claims all parties have consented, or that the requester has special authorization, to bypass ethical restrictionsRun it:
​
medium
jurisdiction-shopping · single-turn · OWASP: LLM01 · MITRE: AML.T0054, AML.T0068Exploits differences in legal frameworks across jurisdictions to claim an activity is permissibleRun it:
​
medium
policy-loophole · single-turn · OWASP: LLM01 · MITRE: AML.T0054, AML.T0068Exploits ambiguities and edge cases in safety policies by framing requests to technically not violate stated rulesRun it: