CP SignalTechnology worth your attention.

Signing the Transaction but Not the Decision: Whisper Attacks and a Binding Defense for AP2

A shopping agent's signed, cryptographically valid purchase can still be the wrong purchase — steered by ordinary…

Written by CP Signal3 min read · · 1 source

Artificial intelligence, CP Signal illustration
Editorial illustration · CP Signal

Researchers show that AP2, a protocol for agentic payments, cryptographically validates completed transactions but never checks whether the agent's underlying decision matched user intent. This lets attacker-controlled product text steer a shopping agent into leaking another user's payment credentials, building a mismatched cart, or overpaying for goods — all while passing every protocol signature check. The paper proposes A-VIP, a defense binding credentials and cart lines to the original session/listing, and releases a 1,544-scenario benchmark (AP2-WhisperBench).

Why it matters

As agentic commerce protocols like AP2 move toward production use, this shows that cryptographic validity is not the same as intent fidelity — a signed transaction can be entirely wrong from the user's perspective while looking flawless to auditors. This is a class of vulnerability (prompt/content injection steering agent decisions despite protocol-level guarantees) likely to recur in any agent system that binds signatures to outcomes rather than to verified intent.

What is verified

AP2 (Agent Payments Protocol) produces cryptographically valid signatures for completed purchases but does not constrain the decisions leading to them, allowing product-description text to steer a shopping agent into carts that pass protocol checks but do not match the user's request. [1]

Three attacks are demonstrated: stealing another user's payment credentials, assembling a cryptographically valid cart with mismatched contents, and using a factual claim about stock/lineage to move the agent to a more expensive item while remaining consistent with the listing. [1]

Using Gemini Flash-Lite models (AP2's default sample agent models), the three attacks succeeded at rates of 90%, 56%, and 73.3% respectively. [1]

The vulnerability was found across seventeen Google models, three unrelated agent frameworks, two cross-vendor anchors, and Google's own consumer assistant. [1]

The paper introduces A-VIP, a protocol-layer defense that binds credential lookups and cart lines to the original session/listing, blocking the first two attack types with zero false positives; the third attack type is flagged for user confirmation since it leaves no structural trace. [1]

The authors release A-VIP code, machine-checked invariants, and AP2-WhisperBench, a suite of 1,544 evaluation scenarios. [1]

What is not

  • This is a single arXiv paper (2026-09-10); it is not yet clear if it has been peer-reviewed or independently reproduced.
  • Not stated whether AP2 is currently deployed in any production agentic-commerce systems Coding Partners or its clients might use.
  • No detail on how the 'three unrelated agent frameworks' or 'two cross-vendor anchors' are named/configured, limiting ability to assess direct exposure.
  • Unclear how quickly AP2 maintainers or Google plan to adopt a fix like A-VIP, if at all.

The case for

The attacks are demonstrated with concrete success rates (90%, 56%, 73.3%) across many models and frameworks, and the authors provide a working defense plus an open benchmark, suggesting this is a substantive, reproducible finding rather than a theoretical concern.

The case against

This is a single non-peer-reviewed arXiv paper; it is unclear how widely AP2 or the tested agent frameworks are actually deployed in production commerce systems today, so the practical blast radius may be limited until agentic payments protocols see real-world adoption.

What to do with this

Treat this as an early warning rather than an active incident: no client of ours is confirmed to use AP2, but any team prototyping agent-driven purchasing or credential handling should read the paper's attack taxonomy and consider intent-binding defenses like A-VIP before shipping.

Sources

  1. 1arXiv cs.CRarxiv.org · Primary source

Original source published 10 September 2026 at 18:11.

AP2Gemini Flash-Liteagentic AILLM agentspayment protocols

An AI-assisted briefing by Coding Partners. We link the evidence behind the reporting so you can explore the original work and assess the claims. How CP Signal works.