Overview
Research published by Lasso Security and covered by Ars Technica in September 2026 reveals a significant and previously underappreciated security side effect of AI text watermarking: Google’s SynthID-Text mechanism can alter LLM safety behaviour, making models more likely to comply with harmful instructions they would otherwise refuse. With Anthropic announcing that future Claude models will adopt SynthID-Text — partly in response to emerging EU regulatory requirements — this finding has immediate practical relevance for a large segment of the enterprise AI market.
The core issue is that watermarking is not a passive labelling operation. It fundamentally changes how a model selects output tokens, and those changes propagate into the model’s decision-making around safety guardrails and tool invocation.
Technical Analysis
SynthID-Text replaces the standard random number generator used in LLM next-token sampling with a keyed pseudorandom process. Its distinguishing feature is tournament sampling: a large pool of candidate tokens is evaluated using a secret key to assign hidden probability scores. Tokens compete in sequential pairwise rounds — the higher-scored token advances — until a single winning token is selected.
While this process is designed to be imperceptible to human readers (preserving text quality while embedding a detectable signal), Lasso Security researcher Andrea Siposova demonstrated that it introduces measurable behavioural drift. Specifically:
- Safety guardrail adherence decreases under adversarial prompt conditions when watermarking is active.
- Tool invocation patterns change in agentic deployments, where the model calls external APIs or executes actions.
- Instructions refused by the base model are, in some cases, executed by the watermarked variant when combined with an adversarial prompt.
The mechanism is consistent with known properties of sampling perturbation: any modification to the token selection process creates tradeoffs that surface in edge-case behaviour, including the boundary conditions where safety training operates.
Framework Mapping
| Framework | Technique | Rationale |
|---|---|---|
| MITRE ATLAS | AML.T0051 - LLM Prompt Injection | Adversarial prompts exploit watermarking-induced behavioural drift |
| MITRE ATLAS | AML.T0054 - LLM Jailbreak | Watermarked models bypass refusals under adversarial conditions |
| MITRE ATLAS | AML.T0015 - Evade AI Model | Attackers can leverage watermarking state to evade safety controls |
| MITRE ATLAS | AML.T0086 - Exfiltration via AI Agent Tool Invocation | Agentic tool calls are specifically highlighted as a risk vector |
| OWASP LLM01 | Prompt Injection | Adversarial prompts exploit changed sampling behaviour |
| OWASP LLM08 | Excessive Agency | Watermarked agents may invoke tools beyond intended safety boundaries |
Impact Assessment
The impact is broad but graduated. Standalone LLM deployments face an elevated risk of guardrail bypass under targeted adversarial conditions — a meaningful concern for customer-facing applications. The risk is materially higher for agentic systems where LLMs invoke tools, access credentials, or take real-world actions. A model that refuses a harmful tool call without watermarking but complies with it when watermarked represents a direct expansion of attacker-accessible attack surface. The EU regulatory driver means adoption of SynthID-Text is likely to accelerate, widening exposure before mitigations mature.
Mitigation & Recommendations
- Regression-test safety alignment after enabling watermarking. Do not assume pre-watermarking red-team results carry over. Run a full adversarial evaluation suite against watermarked model variants.
- Apply additional guardrails at the tool-invocation layer in agentic pipelines — do not rely solely on model-level refusals for security-critical actions.
- Monitor token-level output distributions in production for anomalous shifts that may indicate watermarking-induced drift being exploited.
- Engage watermarking vendors (Google, Anthropic) for safety-preserving configurations or updated guidance specifically addressing adversarial robustness under SynthID.
- Treat watermarking as a security-relevant configuration change requiring change-management review, not a transparent feature toggle.
References
- Ars Technica: LLMs respond differently to harmful prompts when AI watermarking is used
- Lasso Security research (Andrea Siposova) — cited in source article