Loading...
Context Contamination Attack
CCAGradual contamination of conversation context through subtle injections across multiple interactions, slowly corrupting the agent's understanding and behavior.
Example Scenario
Over multiple conversations, subtly introducing false information about security policies, gradually building a contaminated context that the agent trusts, eventually leading to security bypasses.
Testing Objectives
- Test cumulative context validation
- Assess contamination detection
- Evaluate multi-turn security
- Validate context cleaning mechanisms
Defensive Strategies
- Continuous context validation
- Contamination detection algorithms
- Periodic context sanitization
- Multi-turn consistency checks
- Anomaly detection in context
Key Features
- Gradual contamination
- Multi-turn corruption
- Subtle manipulation
- Cumulative effect exploitation
Use Cases
- Context integrity testing
- Multi turn security assessment
- Cumulative effect evaluation
- Contamination detection testing
Tools & Frameworks
Security Risks
Ethical Guidelines
- •Test only with proper authorization
- •Avoid production context contamination
- •Report gradual attack vulnerabilities
- •Focus on improving contamination detection
- •Consider long-term consequences
Remember: This information is for educational and defensive security purposes only. Always ensure you have proper authorization before testing any techniques.
From the engineer behind this catalog
Get your agent system red-teamed
The attacks documented here work on production agent systems every day. Have yours tested before someone else does: prompt injection, jailbreaks, tool misuse and data exfiltration, with every finding written up next to its fix.
€750 instead of €1,500, one week, written report and walkthrough call, until 30 September