Formatting tricks fool LLM judges into accepting wrong answers
Source published ·Modelwire updated
Original coverage: arXiv cs.CL ↗·How Modelwire adds context
The development
Researchers have identified a critical vulnerability in how language models evaluate answers when serving as judges. Subtle formatting changes, such as adding a single colon to structured input, can dramatically shift model verdicts on factually incorrect responses. Testing on DROP and GSM8K benchmarks revealed false acceptance rates jumped from 1-3% to 26% depending on JSON key ordering and presentation style. This finding exposes how brittle current evaluation systems are and suggests that production grading pipelines relying on LLMs may be silently accepting wrong answers based on superficial input formatting rather than semantic correctness. The vulnerability has immediate implications for automated assessment, content moderation, and any system using models as objective arbiters.
Modelwire’s AI-generated summary of coverage from arXiv cs.CL.
Modelwire analysis
ExplainerOur AI-generated reading of the wider context and the next developments to watch.
The paper isolates a specific mechanism: not just that models are sensitive to phrasing (known), but that this sensitivity directly corrupts their ability to reject false answers. The false acceptance rate jump from 1-3% to 26% is the quantified cost of this brittleness in a grading context.
This joins a cluster of findings from the past week showing that LLMs fail silently in high-stakes judgment roles. The depression screening study (October 6) found that model choice, not actual patient data, drove 30% of variance in clinical assessments. The engineering impossibility paper (October 5) showed models can recognize contradictions internally yet still output confident wrong answers. This new work adds a third failure mode: models can be tricked into accepting falsehoods through superficial input changes. Together, these suggest that using LLMs as objective arbiters (whether grading, screening, or reasoning) introduces a hidden layer of unreliability that standard benchmarks don't catch.
If the researchers test the same vulnerability on proprietary models (GPT-4, Claude) and find it persists, that signals the problem is fundamental to how transformers process structured input rather than a quirk of open models. If major LLM evaluation frameworks (like those used by Hugging Face or OpenAI's evals) adopt input-normalization as a standard preprocessing step within the next six months, that's evidence the field is treating this as a known production risk.
This interpretation is generated from the summary above and the archive coverage cited below. Our methodology · Report an error
Coverage behind this analysis
These archive entries ground the connection in our analysis. They are ordered by source publication date, with links to our coverage and the original sources.
·arXiv cs.CL
Language models show more variance than patients in depression screening
A pre-registered study of 880 language-model configurations reveals that model choice, not patient presentation, drives depression screening outcomes. Across 11 open models with varied prompting and scoring strategies, model selection accounted for 30% of symptom-score variance versus just 10.5% for actual participant differences. Critically, two randomly selected raters with identical performance metrics disagreed on screening…
MentionsDROP · GSM8K
How this coverage is produced
Modelwire uses AI to generate summaries and context from source headlines, snippets, and selected archive coverage. Automated checks do not verify every claim, and items are not routinely reviewed by a person before publication. Zacaria Solis operates the site. Read the linked source for the full evidence and report errors through our corrections process.
Modelwire summarizes, we don’t republish. arXiv cs.CL originally reported this story as “Adversarial Cues in Decision Models Used as Judges: The Role of Request Presentation”. The full content lives on arxiv.org. If you’re a publisher and want a different summarization policy for your work, see our takedown page.