Loading...
Memory Persistence Exploitation
MPEExploitation of memory persistence mechanisms to ensure malicious content remains in agent memory across resets, updates, or cleanup operations.
Example Scenario
Crafting malicious memory entries with protected flags or metadata that survive memory cleanup operations, ensuring persistent compromise even after administrator-initiated memory resets.
Testing Objectives
- Test cleanup mechanisms
- Assess reset completeness
- Evaluate persistence controls
- Validate garbage collection
Defensive Strategies
- Comprehensive memory cleanup
- Complete reset procedures
- Persistence validation
- Memory lifecycle management
- Periodic full memory audits
Key Features
- Cleanup bypass
- Reset resistance
- Update persistence
- Garbage collection evasion
Use Cases
- Memory cleanup testing
- Reset mechanism validation
- Persistence control assessment
- Garbage collection evaluation
Tools & Frameworks
Security Risks
Ethical Guidelines
- •Test only with proper authorization
- •Never create persistent production compromises
- •Report persistence vulnerabilities immediately
- •Focus on improving cleanup mechanisms
- •Consider remediation difficulty
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