An agent reading a flattened webpage can mistake text from a third-party element for instructions backed by the page owner or user. Intact introduces GenTree, a representation that retains which script created or changed each DOM element and checks whether an action is compatible with the element's actual web capabilities. The paper describes manipulated…
Inspect the ClaimsCase · DiggingBeagle record
Intact preserves web-element origin to constrain agent actions
In controlled browsing tests, Intact reduces the rate at which poisoned page elements steer agent planning by binding content to browser semantics.
Controlled browser element and prompt-injection evaluation with 1,091 injected pages, not a new real-world website breach.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- demonstrated
- Evidence
- Grade B
- Remediation
- not applicable
- AI role
- AGAINST AI
Basis and provenance
Technical report or researcher-controlled experiments document the stated mechanism, but independent reproduction and population-wide prevalence are not established. Impact band is left unassigned because no calibrated damage threshold or representative victim impact is supported by the available record.
Assessed Oct 20, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-INTACT-RATE · CLM-INTACT-PROVENANCE · CLM-INTACT-OUTCOME-BOUNDARY · Intact: securing agentic browsing with web semantics and element provenance
At a glance
An agent should not grant rendered page text the capability or identity of the browser origin that displayed it.
Read the implicationsGeneralization to authenticated commercial applications and arbitrary DOM instrumentation remains unverified.
Limits and uncertaintyFull account
An agent reading a flattened webpage can mistake text from a third-party element for instructions backed by the page owner or user. Intact introduces GenTree, a representation that retains which script created or changed each DOM element and checks whether an action is compatible with the element's actual web capabilities. The paper describes manipulated pages that elicit unsafe planning in a baseline and a substantial decrease when origin provenance is preserved.
Its evaluation counts reaching a consent stage, not every unauthorized final action. The method also has a measured benign-disruption rate and depends on reliable browser instrumentation, especially at authenticated third-party widgets. It therefore supports a specific origin-aware defense principle without proving universal protection from indirect prompt injection.
The origin issue appears when a third-party widget contributes page text that an agent interprets as the host site's instruction. GenTree retains provenance that flattened rendered content would otherwise erase. The reported outcome measures reaching a consent stage under controlled injections; it is narrower than completing an unauthorized transaction. Browser instrumentation errors and genuine site-authorized widget actions remain important counterexamples.
Timeline
- Oct 19, 2026disclosure
Public disclosure
Claims & evidence
CLM-INTACT-RATEThe study reports lower poisoned-page planning-to-consent success with origin-aware mediation, while not measuring every final unauthorized action.supported
Basis: reported finding
- supportsIntact: securing agentic browsing with web semantics and element provenanceprimary disclosure
Abstract; evaluation and limitations
CLM-INTACT-PROVENANCEIntact uses GenTree to preserve web-element origin and mediate action plans against browser semantics.supported
Basis: reported finding
- supportsIntact: securing agentic browsing with web semantics and element provenanceprimary disclosure
Introduction; System Design
CLM-INTACT-OUTCOME-BOUNDARYThe benchmark counts reaching an attack-planning or consent stage under controlled injected pages; it is not a count of completed unauthorized user transactions.supported
Basis: reported finding
- supportsIntact: securing agentic browsing with web semantics and element provenanceprimary disclosure
Evaluation: attack success definition and consent milestone
Implications
An agent should not grant rendered page text the capability or identity of the browser origin that displayed it.
Unknowns and contradictions
- Generalization to authenticated commercial applications and arbitrary DOM instrumentation remains unverified.
Sources and citation
Material revision history
- Oct 20, 2026 · Canonical change recorded · new in release · revision 177