# Insider Manipulation & Process Corruption — Market/Data Tampering, Legal-Process Subversion & Pretextual Fund Movement (

- **Severity:** High
- **Signature ID:** `75f3511b-0cbe-4bf7-a1a6-f39419bb9ab9`
- **MITRE ATLAS:** AML.T0051 (LLM Prompt Injection)
- **OWASP:** ASI02 (Tool Misuse and Exploitation), ASI03 (Identity and Impersonation), LLM06 (Excessive Agency), LLM08 (Vector and Embedding Weaknesses)

## Summary

This detector flags requests that ask an AI agent with access to trading, legal, or financial tools to manipulate an important process — like market data, a court case, or a fund transfer — while dressing the request up as harmless testing or exploration. The wording sounds innocent ('let's test market response', 'just exploring legal options') but the actual ask is for the agent to do something that corrupts a trusted process for someone's benefit.

## How the attack works

An attacker with access to a business-tool-using agent phrases a manipulative request as a benign exercise: adjusting trading data or moving funds 'to test market response', suggesting incentives for a judge or pressure on a witness 'to assess options', or exporting sensitive data or funding an initiative 'to understand strategic options'. Because there's no fixed phrase or command signature, the manipulation lives entirely in the intent behind ordinary-sounding language, not in any single suspicious keyword. The agent, trusting the pretext, performs the action — moving money, altering data, or acting on a legal matter — believing it is a harmless test or analysis. The detector looks at the meaning of the request rather than matching known bad strings, since regex alone misses this kind of framing.

## Why it matters

An organization could suffer real market manipulation, corrupted legal proceedings (bribery, witness pressure, surveillance of opposing counsel), unauthorized data exfiltration, or unapproved fund transfers — all carried out by a trusted agent acting on a disguised request rather than a technical exploit.

## What you can do

- Require independent authorization checks for any agent-initiated trade, transfer, or legal action, regardless of how the request is worded.
- Treat phrases like 'just to test', 'to explore', or 'to understand strategic options' attached to consequential actions as a review trigger, not an automatic go-ahead.
- Separate agent permissions so no single agent can both propose and execute high-impact financial, legal, or data-export actions without human sign-off.
- Log and periodically audit agent actions on trading systems, legal workflows, and data exports for pretextual justifications that don't match documented business need.

## Known benign look-alikes

- Legitimate review, reconciliation, validation, or compliance checks of trading / financial / legal data
- Properly authorized and compliant transactions
- Anti-fraud or anti-money-laundering review
- Preparing a client's own case with their own materials
- Routine analysis on data the agent is authorized to access

## References

- https://agentthreatrule.org/en/rules/ATR-2026-01809

---
Source: https://www.netzilo.com/threats/atr-insider-manipulation-process-corruption-market-data-tamperin