Security audit
Make
Security checks for vulnerabilities and agentic risk
Overview
This Make integration is broad and can create persistent automations, but the artifacts clearly disclose that behavior and require user approval for writes and automation.
Install only if you intend to let an agent manage your Make account through Maton. Review every proposed write, scenario start, hook, function, trigger, or destination carefully, especially anything that forwards events or runs automatically after the conversation ends. Prefer OAuth through the CLI and avoid exposing API keys or provider credentials in files, logs, headers, or templates.
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.