aifollow.news
Back Rohan Paul
Rohan Paul· @rohanpaul_ai · X· · Original publication time AI score54

RAG retrieval poisoning test finds that repeating user queries can disrupt document rankingsMachine translation

AI introduction

An account of a RAG retrieval poisoning study says researchers added up to five documents repeating each query and tested keyword and semantic retrievers, including BGE-small, across 623 queries. Just five documents, about 0.1% of the corpus, reduced classic retrievers' ranking quality by 40.2% to 61.5%. A filter blocked the query-echoing documents but also reduced clean ranking quality on NFCorpus.

Original post · Original

The article text is unavailable in this language; an existing version is shown.

@rohanpaul_ai

– https://t.co/B1EwwzDgLe

Title: "Reliability Stress Testing of RAG Retrieval under Query-Relevant Corpus Poisoning"

ReplyRohan Paul@rohanpaul_ai
New Google paper on RAG poisoning. Shows that poisoning a RAG system mostly depends on copying the query, since adding an attack payload barely changed which documents got retrieved. fake documents only need to repeat a user’s question to be picked up by AI systems that search before answering, and adding hidden attack instructions barely changed that. RAG systems pull documents from sources that outsiders can sometimes write to. Before any hidden instruction can act, the poisoned page first has to get past the retriever. For each test query, they added up to 5 documents repeating its text, with or without an attack payload. They tested classic keyword and semantic retrievers plus the dense embedding model BGE-small on 623 queries. Just 5 documents, about 0.1% of the corpus, cut classic retrievers' ranking quality by 40.2% to 61.5%. A filter that rejects query-echoing documents blocked them but halved clean ranking quality on NFCorpus, from 0.267 to 0.134. If your RAG index accepts outside content, flag documents that mirror user queries, and measure any filter's cost on clean queries too.
View this post on X ↗

Source: Rohan Paul · x.com

Research
Found an error? Send a correction