Topic starter
03/02/2026 4:22 pm
TL;DR: Exposed instances can leak API keys, OAuth tokens, and conversation histories and even enable remote code execution, while Clawdbot adoption has reached 22% of Token Security’s customers, according to Token Security. The real issue is that autonomous agents with shell access, persistent memory, and broad enterprise permissions break the assumptions behind conventional IAM oversight.
Editorial analysis by NHI Mgmt Group, based on content published by Token Security: “The Clawdbot (Moltbot) Enterprise AI Risk: One in Five Have it Installed”.
By the numbers:
- Token Security found that 22% of its customers have employees actively using Clawdbot within their organisations.
Key questions
Q: What breaks when employees use shadow AI for work tasks?
A: Shadow AI breaks identity visibility and lifecycle control.
Q: Why do consumer AI assistants create more risk than enterprise-tied AI tools in workplace use?
A: Consumer AI assistants can sit outside the enterprise boundary, may use conversations to improve the service, and may allow human review of selected content.
A: Look for any path where the assistant can create, schedule or execute a remediation step rather than only describe one.
Practitioner guidance
- Discover unmanaged AI assistants on endpoints Monitor for process names, directories such as .clawdbot and unusual third-party service connections to identify employees running the assistant outside approved channels.
- Revoke over-broad OAuth grants and API tokens Review connected Slack, Microsoft Teams, Google Workspace and email integrations, then remove any grants that allow an assistant to reach internal channels, files or mailboxes beyond necessity.
- Block exposed agent infrastructure Prevent gateway ports and control servers from being reachable over the internet, and alert on any agent-related infrastructure that accepts unauthenticated access.
Bottom line: Clawdbot turns shadow AI into an identity governance issue because it can inherit enterprise permissions, retain context and act outside normal oversight.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/10/2026 6:42 pm
Shadow AI is now an identity governance problem, not a usage-policy problem. When employees deploy an assistant that can read mail, query Slack and execute commands, the real issue is delegated access scope, not software novelty. Conventional IAM programmes usually govern sanctioned apps and known service accounts, but shadow AI introduces unmanaged runtime identities that still act on enterprise data. The practitioner conclusion is that discovery must be tied to identity ownership and access scope, not app inventory alone.
A question worth separating out:
Q: What should teams do if they discover shadow AI in the business?
A: Teams should first identify who owns the tool, what data it touches, and which identities it uses. Then they should either bring it under policy and lifecycle control or remove access to enterprise data until governance is in place. Discovery without containment simply confirms the scale of the gap.
👉 Read our full editorial: Clawdbot shadow AI exposes a new enterprise identity risk