Papers for

security auditing teams

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Curriculum training improves automated jailbreak discovery in language models

Discovering Jailbreaks via Curriculum of Models

Abstract: Automated jailbreak discovery aims to find prompts that elicit prohibited behaviors from safety-trained language models, helping developers identify vulnerabilities before deployment. One class of approaches uses reinforcement learning to train an investigator model to generate prompts that elicit a specified behavior from a target model. However, training directly against a safety-trained target is difficult because nearly all prompts are refused, leaving the investigator with a sparse reward signal. Prior work addresses this with the propensity bound (PRBO), a proxy reward estimated by sampling responses from a more compliant target, and then adjusting for how likely those responses would have been under the original target. We introduce Curriculum of Models (CoM), an alternative method that trains the investigator against a sequence of modified versions of the target, progressing gradually from a version that readily exhibits the specified behavior to the original target. For jailbreak discovery, training begins against a target version that rarely refuses harmful requests, and advances to the next, harder version once the investigator reliably elicits the behavior from the current one. We evaluate CoM on elicitation tasks involving CBRN materials, explosives, and illicit drugs, using two open-weight targets, gemma-4-31b-it and gpt-oss-120b. We compare against PRBO and direct training on the original target without a curriculum. When the investigator is trained to elicit a single behavior, CoM finds successful jailbreaks more reliably than either baseline. When trained on multiple behaviors simultaneously, the CoM-trained investigator can elicit held-out behaviors, though PRBO-trained investigators achieve higher success rates. Our results suggest that a simple curriculum over target models offers a promising approach for addressing sparse rewards in rare-behavior elicitation.

Wed 28 OctMachine LearningArtificial Intelligence
The gist
It can be very hard to get language models to reveal dangerous or harmful behavior because they usually refuse such prompts. The researchers found a way to teach a system to find these hidden weaknesses by starting with easier versions of the model that say yes more often, then gradually moving to the real, tougher model. This step-by-step approach helps the system discover bad behaviors more reliably than previous methods. It also works when looking for multiple behaviors at once, though some older methods can find more with enough training.
Open → 2610.38833v1

High capacity undetectable collusion between independent language model agents

Codetta: High-Capacity, Keyless, and Undetectable Multi-Agent Collusion

Abstract: Multi-agent systems built on large language models (LLMs) are increasingly deployed in high-stakes settings such as finance, healthcare, and software engineering, where agents coordinate through natural-language messages. The same channels, however, let colluding agents exfiltrate confidential information or coordinate unauthorized actions, and steganography can hide such communication inside outputs that look ordinary to an auditor reading the transcript. Existing provably undetectable LLM steganography protocols are not suited to realistic deployments. High-capacity schemes assume a symmetric setting where the receiver can reproduce the sender's output distribution, the state-of-the-art protocol for asymmetric agents has very low capacity, and most approaches rely on a pre-shared secret key. We make the threat of undetectable agent collusion concrete with Codetta, a high-capacity steganographic protocol for independently deployed agents in realistic asymmetric settings. Codetta combines a shared public model that estimates the communication channel, a sampling mechanism that preserves the sender's output distribution, and an adaptive error-correcting code. It further removes the pre-shared key through a steganographic key exchange that lets independently deployed agents establish a shared key while keeping the transcript computationally indistinguishable from ordinary model outputs. Across three agent workloads and three sender models, Codetta achieves up to $94\times$ the capacity of the state-of-the-art asymmetric protocol, and its key exchange establishes a shared key with about 80k visible tokens at an empirically certified failure probability of at most $4.1\times 10^{-3}$. These results show that effectively undetectable collusion is becoming feasible between independently deployed agents, so auditing must go beyond inspecting communication transcripts.

Thu 24 SeptCryptography and SecurityMultiagent Systems
The gist
Many AI agents communicate using natural language to work together, but some could secretly send hidden messages to cheat or steal information without being noticed. The authors created Codetta, a new way for independent AI agents to exchange secret messages that look like normal conversation and don’t need a shared secret key. Codetta can send much more hidden data than previous methods and even lets agents agree on a secret key without revealing it. This shows that secret cooperation between AI agents can be very hard to detect by just reading their messages.
Open → 2609.28900v1

Adding specifications to prompts cuts errors in AI-generated backend code

Specification Before Generation: A Pre-Registered, Five-Model Paired Evaluation of a Specification Frame for LLM-Generated Code in Money, Time, Idempotency, and Access Tasks

Abstract: Code generated by large language models passes security checks at a rate that has barely moved in four years. In regulated backends, the defect classes that matter most are money arithmetic, time handling, retry safety, and access control. Teams answer with instruction files, yet the largest controlled study of instruction files to date found no benefit. This paper tests a narrower idea: generated code improves when the prompt carries a specification, a fixed preamble stating what must be true of the result. We pre-registered hypotheses, refuters, analysis code, and a one-shot generation rule, then ran 50 realistic backend tasks from finance, healthcare, and insurance practice through five frontier models from five vendor lineages, each task twice: bare, and preceded by a 267-word filled specification frame. Nine deterministic AST-based checkers scored the outputs. The Bandit security scanner, which knows nothing of the frame, scored them independently. The frame reduced defects in all five models (mean reduction 0.16 to 0.70 findings per task, every Holm-adjusted sign test significant, every bootstrap confidence interval excluding zero). Where the arms differed, the frame arm won 95 of 100 times. It never made any model worse in any domain. Bandit found 53 medium-or-high issues in the bare arm and 11 in the frame arm, in the same direction for every model. The effect was largest where a model's unprompted defaults were weakest: the frame supplies the discipline a model lacks. All 500 outputs, prompts, checkers, scoring code, and the pre-registration are published with a DOI, so any team can re-derive the result without trusting the author.

Sun 20 SeptSoftware EngineeringCryptography and Security
The gist
Code made by AI often has bugs in important areas like money calculations, time, retries, and security, and these bugs have not improved much over several years. The authors tested whether giving the AI a clear list of rules or specifications before asking it to write code could help. They found that including these specifications greatly reduced mistakes across multiple AI models and different kinds of backend tasks. The improvements were biggest where the AI’s usual guesses were weakest, showing that clear instructions help guide the AI to safer code.
Open → 2609.23270v1

Scaling zero knowledge UNSAT verification reduces memory use and boosts certification

Scaling Zero Knowledge UNSAT Verification via Normalized Chaining

Abstract: Proofs of UNSAT are a standard primitive in formal verification and software assurance. In many real-world settings, the proof itself encodes proprietary or security-sensitive information, making public disclosure undesirable. Zero-knowledge certification of UNSAT addresses this tension: it enables a prover to convince a verifier that no satisfying assignment exists, without revealing anything about the underlying proof beyond its validity. Luo et al. recently introduced ZkUnsat, a protocol that achieves this goal by proving the validity of a weakened resolution proof in zero knowledge. ZkUnsat demonstrates the feasibility of zero-knowledge certification; however, its scalability to larger, real-world instances is constrained by substantial prover memory overhead, limiting its real-world applicability. Motivated by advances in UNSAT proof formats such as LRAT, which enable efficient plain-text verification, we present a preprocessing technique that improves the efficiency of ZkUnsat without introducing additional leakage. Our approach normalizes the proof so that each derived clause is justified by a resolution chain of fixed public length k. This eliminates chain-length leakage and reduces prover memory usage. With k = 16, our method certifies roughly 62% more instances than baseline ZkUnsat on the SAT 2002 competition benchmarks. Furthermore, for an equivalent number of certified instances, the memory footprint drops to under 25% of that required by the baseline.

Wed 16 SeptCryptography and SecurityLogic in Computer Science
The gist
Checking that certain logic puzzles have no solutions is important for software safety, but sharing how you proved this can reveal secrets. The paper improves a method that lets one prove no solution exists without revealing any details, but previous ways used too much memory making them hard to use. The authors propose a way to standardize part of the proof, cutting memory needs and allowing more puzzles to be checked efficiently. This means privacy-preserving proof methods can work better on bigger, real problems.
Open → 2609.19353v1

TasmScan improves smart contract analysis for TON virtual machine

TasmScan: Continuation-Aware Taint Analysis for TVM Bytecode with Savelist Abstraction

Abstract: The Open Network (TON), with a peak market capitalization exceeding $20 billion and over 175 million activated on-chain addresses, relies on the TVM (TON Virtual Machine) to execute smart contracts. TVM uses first-class continuations with savelists to manage control flow and register state across continuation invocations. Since savelist-captured registers allow data to flow across continuation boundaries without passing through the operand stack, bytecode-level analyses cannot construct complete data flow tracking without explicitly modeling savelist semantics. We present TasmScan, the first bytecode-level static analysis framework for TVM that enables cross-continuation data flow reasoning without requiring source code. TasmScan models savelist semantics via forward register analysis with a formal over-approximation guarantee for exact-resolved save sites and locally tracked register definitions, then lifts bytecode into TASIR, a typed intermediate representation, and performs path-sensitive taint analysis with context-aware sources to detect defects. We evaluate TasmScan on 2,921 contracts from the TON verifier registry and a labeled benchmark of 208 contracts with human-confirmed ground truth. On the full corpus, TasmScan resolves 294,546 dynamic continuation targets with 100% precision; ablation confirms that savelist propagation is essential for resolving indirect register calls that depend on cross-continuation register passing. On the benchmark, TasmScan detects 95.3% of defects across five classes with 96.8% precision. A 366-pair stratified sample from the full corpus estimates 85.8% overall precision. TasmScan offers a 17x median speedup over the state-of-the-art symbolic-execution baseline, and in the path-analysis comparison completes 100% of analyses with zero crashes or timeouts.

Tue 15 SeptSoftware EngineeringCryptography and Security
The gist
Smart contracts on the TON network run on its own virtual machine called TVM, which uses a unique way to manage the flow of instructions and data. The authors explain that existing tools can miss important data flows because of how the TVM handles continuations and register states with something called savelists. They created TasmScan, a tool that better tracks these complex data flows without needing the original source code, making it easier to find bugs in TVM smart contracts. When tested, TasmScan was very precise and fast compared to previous methods.
Open → 2609.16987v1

Automated program repair agents often produce unsafe code when attacked

Adversarial Testing of Automated Program Repair Agents for Security Vulnerabilities

Abstract: Software agents with Large Language Models (LLMs) are designed for Automated Program Repair (APR) tasks, raising the possibility that, in the near future, APR agents will fix bugs automatically without much human intervention. Can we trust an APR agent to produce both functionally correct and secure code in such situations? What if attackers target production APR agents with adversarial issues that seem benign but may influence the agents to produce correct but insecure code? In this paper, we took a first step towards answering these questions by conducting an empirical study. First, we created SWEADV, a benchmark of 750 adversarial issue descriptions constructed from 150 repair tasks in SWE-bench Verified. For each repair task, we created five adversarial issue descriptions, one for each attack type: command execution, deserialization, path traversal, denial of service, and weak hashing. Second, we evaluated mini_swe APR agents from three LLM backends on SWEADV: GPT-5-Mini, MiniMax-M2.5, and DeepSeek-R. We found that on average, adversarial issue descriptions can induce malicious behaviors with successful repair in 51.7% of cases. Third, we investigated whether typical detection mechanisms are sufficient to prevent such malicious patches from being accepted. Pre-repair detection with LLM-as-judge on the adversarial issue descriptions resulted in an average detection accuracy of only 62.3%. Post-repair detection on adversarial APR patches using static analysis tools and LLM-as-judge achieved average detection accuracies of only 39.4% and 55.4%, respectively. We conclude that autonomous APR agents cannot be trusted yet in production deployment, given their susceptibility to adversarial attacks.

Mon 14 SeptCryptography and SecuritySoftware Engineering
The gist
Software tools that automatically fix bugs using advanced AI models might not always create safe code. The authors tested these tools with specially designed tricky problems meant to fool them. They found that about half the time, the AI fixed the code but introduced security risks. Current methods to detect these unsafe fixes are not very reliable. This means we cannot yet fully trust these automatic bug-fixers to safely repair code without human checks.
Open → 2609.15963v1