Secret Scanner Agent: Extracting Secrets and Access Context from Unstructured Documents
Zixiao Chen, Mariko Wakabayashi, Charlotte Siska
cs.CR, cs.MA
Submitted: 2026-07-10
Comments: Submitted to the Conference on Applied Machine Learning for Information Security (CAMLIS) 2026
Code: https://github.com/karolzak/support-tickets-classification
License: http://creativecommons.org/licenses/by-nc-nd/4.0/
The gist: Exposed documents such as emails, chat threads, tickets, and incident notes routinely leak credentials, but during incident response a leaked secret is only half the story.
Terminology
Abstract
Exposed documents such as emails, chat threads, tickets, and incident notes routinely leak credentials, but during incident response a leaked secret is only half the story. Responders also need to identify the ``door'' the secret opens: the account, tenant, endpoint, database, cloud resource, or other system that the credential could allow an attacker to access. Traditional secret scanners rely on regular expressions or trained classifiers which work well on well-formatted code, yet they struggle when a credential is fragmented, reformatted, or far from the resource it unlocks, and they report the secret string without naming what it opens. We present Secret Scanner Agent (SSA), a multi-agent large-language-model system that extracts both the secret and its associated door, together with supporting evidence, from unstructured exposed documents. SSA pairs a detection agent that favors recall with a review agent that filters false positives and recovers missing context. Because real credential data is sensitive, we evaluate SSA on synthetic benchmarks we generated that span 23 secret types and multiple document formats, scored with a three-step pipeline of programmatic matching, an LLM judge, and human review. Across six models, multi-agent SSA improves extraction precision over a single-agent variant, with the largest gains on door extraction, by up to 16 percentage points. SSA matches a regular-expression scanner's precision while more than tripling its recall, and against thirteen security analysts it is more precise, recovers nearly twice as many secret--door pairs, and runs five to seventeen times faster. By returning the secret, its door, and supporting evidence in one result, SSA turns credential detection into an actionable finding for triage and remediation.
Sources
- UTNLP at SemEval-2022 Task 6: A Comparative Analysis of Sarcasm Detection Using Generative-based and Mutation-based Data Augmentation
- Secret Leak Detection in Software Issue Reports using LLMs: A Comprehensive Evaluation
- Machine Learning vs Deep Learning: The Generalization Problem
- Detecting Hard-Coded Credentials in Software Repositories via LLMs
- Improving Factuality and Reasoning in Language Models through Multiagent Debate
- You Have Been LaTeXpOsEd: A Systematic Analysis of Information Leakage in Preprint Archives Using Large Language Models
- ChatGLM: A Family of Large Language Models from GLM-130B to GLM-4 All Tools
- MetaGPT: Meta Programming for A Multi-Agent Collaborative Framework
- CAMEL: Communicative Agents for "Mind" Exploration of Large Language Model Society
- Source2Synth: Synthetic Data Generation and Curation Grounded in Real Data Sources
- Self-Refine: Iterative Refinement with Self-Feedback
- A survey on bias in machine learning research
- ChatDev: Communicative Agents for Software Development
- Secret Breach Detection in Source Code with Large Language Models
- Reflexion: Language Agents with Verbal Reinforcement Learning
- AutoGen: Enabling Next-Gen LLM Applications via Multi-Agent Conversation
- ReAct: Synergizing Reasoning and Acting in Language Models
Related papers
- SoK: AI-Augmented Binary Reversing
- Relaxed Sender Anonymity for CBDC Interbank Settlement: A Zero-Knowledge Approach on Permissioned EVM
- Calibration-Family Overfit: Why Trusted Sabotage Monitors Don't Transfer Across Lineages
- Efficient Fuzzy PSI under One-Sided Assumptions
- Sealing the Audit-Runtime Gap for LLM Skills
- Token Composition: A Graph Based on EVM Logs