Security audit
quo
Security checks for vulnerabilities and agentic risk
Overview
This is a disclosed Quo business phone integration that uses Maton for OAuth, API calls, and optional user-approved automations.
Install only if you intend to let Maton mediate access to your Quo account. Review each connection, write action, hosted function, trigger, destination, or webhook before approving it, because those can expose phone records, messages, contacts, recordings, or ongoing event data. Prefer OAuth/CLI use over raw API keys and avoid third-party destinations unless you explicitly trust the host and understand what data will flow there.
Vulnerability Patterns
- Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
- Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
- Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
- Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
- Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
- Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
- Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Static analysis
No suspicious patterns detected.