WAAA! Web Adversaries Against Web Agents

summary

The gist

Large language models (LLMs) are increasingly being integrated into web browsers to create agentic browsing systems that execute actions behalf of the user.

In short

This research proposes a new threat model for agentic browsers, moving beyond simple prompt injection attacks to include traditional web social engineering. It identifies 20 specific attacks across the web and LLM spaces, categorizing risks based on browser properties and attacker capabilities. The findings necessitate re-architecting agentic browsers with a security model aligned with these threats.

Key concepts

Confused Deputy Model
This concept views the LLM agent in an agentic browser as a 'confused deputy.' Because the agent struggles to distinguish between its assigned task steps and standard web attacks, it can be tricked into performing unintended actions that violate security boundaries.
Browser Properties and Attacker Properties
The threat model structures security risks by looking at two main dimensions: what the browser itself offers (Capabilities and Input Data) and what the attacker possesses (Capabilities and Target). This framework helps map how specific browser features can be exploited by different types of malicious actors.
Failure Modes
The study distills complex threats into five broad failure modes that agentic browsers exhibit when facing web threats. These include agents bridging data across sites, hallucinating URLs, and misusing integrated tools. Understanding these common outcomes is crucial for designing effective defenses.
Taxonomy of Attacks
The paper develops a structured list of 20 attacks categorized by four dimensions: Browser Properties, Attacker Properties, Browser Capabilities, Input Data, Attacker Capabilities, and Attacker Target. This taxonomy provides an expert-guided map for understanding the entire attack surface.

Terminology used across episodes

This episode discusses

The paper

WAAA! Web Adversaries Against Web Agents · Read on arXiv

North Carolina State University

Large language models (LLMs) are increasingly being integrated into web browsers to create agentic browsing systems that execute actions on behalf of the user. Prior work considering the security of agentic browsers focuses on indirect prompt-injection attacks. However, by failing to consider traditional web attacks, previous agentic browser threat models have a blind spot to web social engineering attacks originally designed to trick humans. In this paper, we propose the first web-focused threat model for agentic browsers and use it to derive a taxonomy of 20 attacks across both the web and LLM space, and implement 18 of the attacks. Our threat model extends the original See to Act browser agent model to account for all components of a browser, and frames the agent as a confused deputy unable to distinguish task steps from traditional web attacks. We show that 10 web threats can reemerge often in amplified forms once an agent can be influenced by untrusted page content. We further conduct a generalizability study on 14 of the 20 attacks, showing that our attacks reproduce across 4 major LLM models spanning multiple vendors. We show that agentic browsers exhibit five major failure modes when facing traditional and LLM web threats, demonstrating the need to rearchitect agentic browsers before they are ready for the current web.

Transcript

Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.

Nadia: We're looking at the paper: "WAAA! Web Adversaries Against Web Agents".

Elias: Here's the gist of the paper. Large language models (LLMs) are increasingly being integrated into web browsers to create agentic browsing systems that execute actions behalf of the user.

Nadia: This paper proposes the first web-focused threat model for agentic browsers and uses it to derive a taxonomy of 20 attacks across both the web and LLM space.

Elias: The Core Problem Identified The authors argue that prior work on agentic browser attacks focuses exclusively on indirect prompt-injection attacks, failing to consider traditional web social engineering attacks originally designed to trick humans.

Nadia: The key insight is that the LLM agent in an agentic browser is a confused deputy unable to distinguish task steps from traditional web attacks.

Title and authors: Nadia: So we've talked about what the paper is calling "WAAA! Web Adversaries Against Web Agents" and how it sets up a framework for understanding these threats. We also touched on the broad scope of agentic browsers being analyzed.

Elias: Right. To get into the nitty-gritty, let's look at how they define this threat model itself and what its structure is supposed to achieve for defense researchers.

Priya: I’m thinking about how this framework helps us move past just looking at single attack types and start seeing the bigger picture of a system's vulnerabilities.

Nadia: They combine existing agentic models with traditional browser security, using two main dimensions: browser properties like capabilities and input data, versus attacker properties like capabilities and target.

Elias: That structure lets them categorize attacks based on what the agent is *given* versus what the attacker *wants* to achieve.

Priya: So if we look at the taxonomy of twenty attacks they derive, how does that structure help us figure out where to focus our testing efforts <ref:2605.05509#pg1>?

Nadia: It helps because it shows how attacks depend on both the capabilities provided to the agent and what the attacker is aiming for.

Elias: And they show that their attacks reproduce across four major LLM models from different vendors in a generalizability study on fourteen of them <ref:2605.05509#pg2,a generalizability study on 14 of>.

Priya: That reproducibility across models is a strong signal, it suggests these are fundamental issues with the architecture rather than just quirks of one specific AI implementation.

Nadia: Right, and they distill their findings into five major failure modes that apply to both traditional and LLM web threats: agents bridging cross-site data, same-site data, hallucinating URLs, websites attacking the LLM itself, and misusing integrated tools.

Elias: And they show these five failure modes manifest even when facing traditional web attacks.

Priya: That’s a lot of ground to cover in terms of defense strategy if you’re trying to secure this space.

Nadia: The implication is that we need to move away from retrofitting safety and toward rearchitecting the browser security model itself to align with this specific threat taxonomy.

The paper's summary: Elias: So, building on what we said, let’s unpack the core summary of "WAAA! Web Adversaries Against Web Agents." What is the fundamental problem they identified in their research?

Nadia: They found that prior work has been too narrow, focusing only on indirect prompt-injection attacks. This leaves a big blind spot for traditional web social engineering attacks aimed at tricking humans directly.

Priya: So, the authors are saying that we're missing the human-centric part of the attack surface when we look at agentic systems?

Elias: Precisely, they argue that the LLM agent is a confused deputy incapable of distinguishing between its required task steps and these older, traditional web attacks.

Nadia: They take the original See→Act model and expand it to include every component of a browser—the rendering engine, the agent reasoning, all those pieces.

Priya: If you're modeling an entire system like that, what does that actually mean for understanding how data flows?

Elias: It means they are accounting for more than just the LLM's output; they’re looking at how the browser interacts with the page and its tools.

Nadia: They propose this new web-focused threat model specifically to map out these broader attack vectors systematically using that See→Act foundation.

Priya: So, when you look at their twenty attacks, what's the main takeaway about how these attacks are structured <ref:2605.05509#pg1>?

Elias: The structure itself is key; it shows that the success of an attack depends heavily on the specific capabilities handed to the agent and what resources an attacker has available.

Nadia: It’s not just about a single exploit code; it's about mapping out dependencies across those four property dimensions they defined.

The paper's improvements: Nadia: Now that we know what the problem is, the authors suggest specific improvements for how we should approach defending these systems based on their threat model.

Elias: They argue that meaningful protection requires a rearchitecture of agentic browsers around this new security model instead of just patching existing designs.

Priya: So, what kind of architectural changes are they suggesting? Are we talking about adding more filters or changing the core design philosophy?

Nadia: They suggest limiting capabilities to the absolute minimum required for a specific workflow to drastically reduce the attack surface.

Elias: That’s a practical constraint; if an agent doesn't need access to, say, general browser UI functionality, it shouldn't have it by default.

Priya: That ties back into my earlier point about trust—they suggest enabling developers to annotate web content with trust levels on the site itself.

Nadia: Right. This addresses the problem where there’s no clear notion of trust within content on the same site, letting the agent make more informed decisions about what to be cautious of.

Elias: They also propose using static or semi-static rules that reflect those common failure modes to intervene when actions would break established boundaries.

Priya: So, it’s a mix of architectural limits, content trust signals, and runtime rule enforcement all at once.

Conclusion: Nadia: To wrap up this discussion on "WAAA! Web Adversaries Against Web Agents," the authors conclude that agentic browsers need to be rearchitected before they can handle the current web environment effectively.

Elias: They summarize that all twenty attacks studied result in those same five failure modes, which means fixing one type of attack won't solve the whole problem <ref:2605.05509#pg1>.

Priya: So, if you had to distill this for someone just listening to the show who doesn't read research papers, what’s the single most important thing they want you to know?

Nadia: The core contribution is establishing an expert-guided taxonomy of attacks against agentic browsers that gives us a foundation for future work.

Elias: It’s providing that map, showing exactly where the security gaps are and what kind of defenses are needed based on their threat model.

Priya: It’s a necessary step to move from just hoping the models align well to actually building systems that are resilient against real-world manipulation.

More episodes

← Home