You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HackAgent’s RAG attack poisons documents for indirect instruction following at retrieval time. It does not yet implement AgentPoison-style memory/RAG backdoors: optimized triggers mapped into a unique embedding region so that, when the user instruction contains the trigger, malicious demonstrations are retrieved with high probability while benign queries stay clean.
That is a different threat model from one-shot document instruction injection: stealthy backdoor triggers, low poison rate, and transfer across agent memory stores.
Taxonomy
Field
Value
Primary category
adaptive
Tags
indirect, rag
Register as AttackCategory.ADAPTIVE + AttackTag.INDIRECT + AttackTag.RAG.
Adaptive: trigger/payload optimization over retrieval success. Distinct from current rag technique, which is classified static (poison once, then query) — this issue is a new attack_type (e.g. agentpoison / memory_backdoor), not a rename of rag.
Scope for v1
Optimize or search for a backdoor trigger that co-locates poisoned memory/RAG entries in embedding space.
Inject a small poison set into agent long-term memory or RAG KB.
Evaluate: triggered instructions retrieve malicious demos and induce attacker-chosen behavior; untriggered instructions remain near baseline utility.
Target at least one HackAgent-supported agent path (RAG-backed or memory-backed).
Activity