@inproceedings{augey-etal-2026-rapids,
    title = "{RAPIDS}: Resume Attack Prompt Injection Detection at Scale",
    author = "Augey, Yohann  and
      Levy, Joshua H.  and
      Akdemir, Arda",
    editor = "Li, Yunyao  and
      Rehm, Georg  and
      Tu, Mei",
    booktitle = "Proceedings of the 64th Annual Meeting of the {A}ssociation for {C}omputational {L}inguistics ({ACL} 2026)",
    month = jul,
    year = "2026",
    address = "San Diego, California, USA",
    publisher = "Association for Computational Linguistics",
    url = "https://preview.aclanthology.org/ingest-acl/2026.acl-industry.127/",
    pages = "1848--1865",
    ISBN = "979-8-89176-394-4",
    abstract = "The integration of Large Language Models (LLMs) into recruitment workflows has introduced a critical security vulnerability: indirect prompt injection attacks embedded within resumes can manipulate screening tools to override instructions, effectively jailbreaking the hiring process. Frontier LLMs can detect such anomalies, but deploying them at the scale required for high-volume recruitment is prohibitively slow and costly. At the same time, existing generic prompt injection detectors lack the domain specificity needed for nuanced resume attacks. To address this gap, we introduce RAPIDS, a scalable detection framework with three contributions. First, we release a synthetically generated dataset of injection snippets derived from curated attack seeds spanning multiple adversarial strategies to address data scarcity in this domain. Second, we fine-tune a lightweight Small Language Model (SLM) on this data that outperforms the best off-the-shelf detector by over 50{\%} in relative F1 and approaches frontier LLM accuracy. Third, we propose a cascade architecture in which the fine-tuned SLM serves as a high-recall first stage followed by an LLM verifier. This design achieves ${\geq}$ 98{\%} end-to-end recall on both evaluated datasets while delivering a $21-24\times$ latency reduction over standalone frontier LLMs (GPT-5-mini), bringing expected per-request latency to $115-171$ ms at roughly 3.5{\%} of the API cost."
}