T08 · Insecure Dependencies
Error
- Location
SKILL.md:17- Finding
Unpinned Third-Party Package and Repository Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Percept Meetings
Security checks for vulnerabilities and agentic risk
Overview
The skill is purpose-aligned for meeting search, but it handles highly sensitive meeting data with broad activation, weak privacy guidance, and unsafe setup patterns.
Review before installing. Only use this skill for meetings and accounts you are authorized to access, run Percept in an isolated environment, pin and verify the dependency, restrict database access, obtain participant consent for recording or ambient capture, scope searches/imports narrowly, and avoid URL query-string webhook tokens where possible.
Vulnerability Patterns
- Insecure DependenciesIntroduces malicious components through unsafe dependency sources
- Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
- 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
Findings (2)
T09 · Insecure Skill Coding Practices
Warning
- Location
SKILL.md:34- Finding
Webhook Authentication Secret Exposed in URL Query Parameter
- Content
View full analysis
- Remediation
View remediation
` header. 2. If the Omi client cannot set authorization headers, use a signed-request mechanism with a timestamp, nonce, and HMAC rather than a reusable URL token. 3. Configure web servers, proxies, gateways, monitoring tools, and tracing systems to redact authentication material. 4. Rotate any webhook tokens that may already have appeared in URLs or logs. 5. Use separate, high-entropy secrets for each deployment and environment. 6. Enforce token expiration or periodic rotation where supported. 7. Add replay protection, request-size limits, rate limiting, and strict transcript payload validation. 8. Update all documentation so that the stated bearer-token requirement matches the actual setup procedure. ]]>
Vulnerability Patterns
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
- Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)
Missing User Warnings
High
- Category
- Not specified by scanner
- Confidence
- 95% confidence
- Finding
The skill documentation explains how to ingest data from Zoom, Granola local caches, and Omi webhooks, but does not clearly warn users that it accesses potentially sensitive transcripts, speaker identities, local meeting caches, and action items. In this context, the omission is risky because users may enable the skill without understanding the privacy implications, retention in SQLite, or the possibility of exposing confidential business discussions through agent workflows.
- Content
Vague Triggers
Medium
- Category
- Not specified by scanner
- Confidence
- 96% confidence
- Finding
The skill metadata advertises very broad trigger phrases such as generic references to meetings, follow-ups, scheduling based on discussions, and 'what did [person] say,' which can cause the skill to activate in many ordinary conversations. Because this skill imports and searches highly sensitive meeting transcripts, over-broad routing increases the chance that private transcript data is accessed or surfaced when the user did not explicitly intend to invoke this capability.
- Content
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 96% confidence
- Finding
The documentation promotes ambient audio capture, possible cloud transcription, webhook transmission, and storage/searchability of meeting content without warning about consent, legal compliance, retention, or sensitive-data exposure. In a meeting-context skill, this is especially risky because captured content may include confidential business discussions, personal data, or regulated information, and users may infer the setup is safe to deploy broadly as written.
- Content