grokbot atlas / pain-points / per-user-isolation-injection

← Back to pitfall

Pitfall

Per-User Isolation Leaves a Prompt-Injection Surface

A security analysis argues that shared user sessions are not the same as isolated security boundaries between bots.

salesbrowserautomationresearch

What happened

If one bot reads untrusted email while another can access a CRM or payment system through the same identity, malicious content may cross the boundary. Treat every external page and message as untrusted input, and separate credentials wherever the product allows it.

Editorial use

Why this belongs in the atlas

Treat this as a risk note: start with least privilege, supervise the first run, and keep a rollback path.

Research provenance

Compiled from the linked source and archived research notes on September 2, 2026.

This independent summary is intentionally concise. Copyright remains with the original authors and publishers; use the source record to read the full material.