ClawAudit verdict
microsoft-365-graph-openclaw
Microsoft 365 Graph integration using standard OAuth device code flow with explicitly documented scopes and security notes about protecting tokens.
⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.
Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.
Findings (7)
References sudo — requests elevated privileges
docs/minimal-setup.md · code · sudo
HTTP request to bare IP address — common in malicious payloads
references/mail_webhook_adapter.md · code · http://127.0.0.1
Possible hardcoded credential
scripts/diagnose_mail_webhook_e2e.sh · prose · downgraded · TOKEN="$(read_env_value OPENCLAW_HOOK_TOKEN || true)
Accesses OpenClaw config/secrets directly
docs/minimal-setup.md · prose · downgraded · ~/.openclaw/openclaw.json
apt-get install — installs system packages
scripts/setup_mail_webhook_ec2.sh · prose · downgraded · apt-get install
Popular HTTP library — network access
scripts/run_mail_webhook_smoke_tests.sh · prose · downgraded · got
Python os.getenv — reads environment variable
scripts/utils.py · prose · downgraded · os.getenv(
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class A). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
Requires 3 system binaries. (1 elevated: curl).
Is this flag fair?
Thanks — recorded.