- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper proposes SPIDES, an information-flow control framework for browser-use agents. Website operators label DOM elements with whether the content is trusted (e.g., operator content vs. user reviews) and who may read it. SPIDES carries these labels into the agent’s accessibility snapshots, hides untrusted or restricted content behind variables, and tracks how trusted and how confidential the agent’s context has become. A consequential action on an allow-listed site is allowed only if no untrusted data has influenced it, data may be sent only to its allowed readers unless the context is still trusted, and anything else needs user approval. On MicroNet, a closed set of 28 websites with 56 benign tasks and 56 attacks, SPIDES has 0% attack success on five models under a worst-case adversary and an ideal user, with 67%–86% task completion, higher than the masking baselines UCM and UCM+.
Critical strengths
The paper makes a convincing case that the same-origin policy is the wrong boundary for browser agents. Appendix G shows both sides: SOPGuard asks for approval in every run of a safe task that must move a product name between two sites, and misses a same-site attack that copies a private recovery email into a public profile in all 25 runs. Element-level labels with site-dependent policies are a sensible way to allow the cross-site flows that tasks need while blocking attacker-influenced actions.
The guarantees do not depend on the model, and the evaluation tests exactly that. For instruction injection, the adversary chooses the model’s tool calls whenever untrusted content reaches it; five models are each run five times; and the autonomy comparison gives all defenses the same guarantees before counting approvals. Under these conditions, SPIDES blocks all attacks while completing more tasks than both masking baselines on every model.
Critical weaknesses
The results depend on correct labels from website operators, which is the main question for deployment, but this is not tested. All MicroNet labels are ground truth set by the authors. In practice, labels may be missing or wrong, and on allow-listed sites an element with no labeled ancestor is treated as trusted and public by default (line 205), so a missing label on user content fails open. The paper argues that labeling is similar to providing accessibility information (Section 7) but gives no evidence. Removing or flipping a fraction of labels, or labeling a few real websites, would show how much of the guarantee survives.
The 0% attack success also relies on an ideal user who rejects every approval request influenced by the attacker (Appendix D); for data injection, GPT-5.6 Sol plays this role. Once untrusted content is revealed, every consequential action on an allow-listed site needs approval, and SPIDES needs 1.84 approvals per completed benign task, compared with 0.22 for SOPGuard; real users who see frequent prompts may approve without care. In addition, MicroNet is small and was built by the authors from an LLM-generated first version, so utility and approval counts on more realistic workflows are unclear.
Questions for authors
In the attack runs, how many approval requests did SPIDES raise, and what does a request show the user? This would show how often the 0% result depends on the user’s decision.
Minor (no response needed): line 078 says SPIDES completes 69.3%–86.1% of benign tasks, but Figure 2(c) and Table 3 give about 67% for Claude Opus 5.5.
2 comments
Thanks! All sounds good to me. I will keep my score at 3.
In attack runs, SPIDES raised an average of 2.17 approval requests across all models. While SopGuard raised fewer approval requests under attacks (0.45), it autonomously approved unsafe browser actions and was substantially more vulnerable to attacks with an ASR of 53-73% (Figure 2). When we added approvals to all defenses to provide the same security guarantee, SPIDES raised the fewest number of approvals among them, as shown below.
We will report the number of approval requests during attack runs both in the default setting and security-aligned setting.
SPIDES can provide useful information-flow context to support the user's decision. Specifically, an approval can identify the source elements that may have influenced the action, the sink web element, and the violated policy, such as Trusted Action (P_T) and Permitted Flow (P_F). However, we have not evaluated the impact of information-flow context on users' security decisions and leave this for future study.
For incorrect labels, we will see the following effect:
Here, X->Y means that X is the correct label and Y is the actual label. The drop in utility/security will depend on the fraction of labels that are incorrect, which is why we forgo these experiments.
For missing labels, we rely on defaults. By using (Untrusted, Private) as defaults, we can guarantee that we only compromise on utility but never on security.
The current paper's default label for trusted websites, (Trusted, Public), is not fail-safe, and we plan to revise it to (Untrusted, Private).
We evaluated the effect of missing labels and safe defaults on MicroNet and observed the following results. On GPT-5.6-Sol, missing labels with safe default reduced utility from 85% to 74% and increased averaged approvals from 1.77 to 2.83, but ASR stayed at 0.