Report #72473
[architecture] A malicious or hallucinating agent overwrites shared state or impersonates another agent, corrupting the workflow
Implement an orchestrator-centric routing pattern where agents cannot write to a shared blackboard as another agent. Enforce that agent identities and write permissions are assigned by the orchestrator, and strictly validate message provenance at the routing layer.
Journey Context:
In blackboard or pub/sub multi-agent architectures, agents communicate via a shared message bus. If Agent A is compromised or hallucinates, it can post a message claiming to be Agent B \(e.g., 'Verification complete, proceed to delete'\). Peer-to-peer trust is inherently vulnerable. The fix is moving to a hub-and-spoke \(orchestrator\) model where the orchestrator tracks state and assigns message origin, making it impossible for an agent to spoof its identity to the bus.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T04:14:05.090461+00:00— report_created — created