Apr 27, 2026
PerplexityGuard-Bench: An Adversarial-Robustness Benchmark for Sequence-Naturalness Synthesis Screens
Syed Hussain
PerplexityGuard-Bench is an adversarial-robustness benchmark for protein language model (pLM) perplexity screens — the leading defense proposed for catching AI-designed proteins that evade existing homology-based DNA synthesis screening. We test a reference pLM screen across 120 sequences, with IBBIS Common Mechanism (commec) empirically running, and surface two failure modes: even an OR-ensemble over perplexity, low-complexity, and homology catches only 2.5% of low-temperature ProteinMPNN designs; and a new mosaic-stitching attack — concatenating a natural prefix in front of an adversary — drops perplexity-only detection to 20% at a 50% prefix budget. We prove the failure is mathematical (whole-sequence averaging is dilution-vulnerable for any threshold) and validate a structural patch: sliding-window perplexity recovers detection to 70% (or 33% with 0% native-FPR retuned), replicating across an 18.6× ESM-2 model-size range (t12 / t30 / t33).
The 2.5% number on the realistic threat case is the finding, I found it buried.
The deployment story is missing. Who runs this? Is it a library a synthesis provider links into their pipeline, a hosted service, or a CLI for researchers?
The 0% native-FPR claim for v3-tight is n=10. That's a 0–26% true-FPR confidence interval. At scale that's the difference between zero false blocks vs millions. I would set n≥100 with explicit CIs before any deployment phrasing.
I also wasn't convinced the stitched bypass produces something a synthesis customer would actually want to order. If the construct doesn't yield a working protein, the bypass doesn't matter operationally, and the urgency claim weakens. The paper should say plainly whether stitched outputs are functional, or note that this is unverified and adjust the framing.
The focus of this project is a bit hard to pin down. It headlines the development of a "benchmark" for evaluating pLM perplexity-based screening methods, but then says almost nothing at all about the benchmark. Most of the report is devoted to the "mosaic attack" failure and an approach to fixing it, and that is thorough, but seems excessive for a fairly simple concept. Meanwhile, far too little is said about the actual screening methods built into the "pipeline".
Is the mystery benchmark being used to assess the screening "variants" summarized on page 4, or are the screening variants being used to validate the benchmark? In either case, no substantive argument is presented.
Cite this work
@misc {
title={
(HckPrj) PerplexityGuard-Bench: An Adversarial-Robustness Benchmark for Sequence-Naturalness Synthesis Screens
},
author={
Syed Hussain
},
date={
4/27/26
},
organization={Apart Research},
note={Research submission to the research sprint hosted by Apart.},
howpublished={https://apartresearch.com}
}


