configure-notifications

Fail

Audited by Snyk on Mar 24, 2026

Risk Level: HIGH
Full Analysis

HIGH W007: Insecure credential handling detected in skill instructions.

  • Insecure credential handling detected (high risk: 1.00). This skill explicitly asks the agent to collect user tokens/webhook URLs and to embed them verbatim into config files, curl commands, test requests, and printed summaries, which requires the LLM to handle and output secrets directly.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (high risk: 0.80). The skill explicitly fetches and parses untrusted, user-generated third-party content as part of its runtime workflow (e.g., Telegram getUpdates in "Telegram Setup" Step 4 to extract chat IDs and the Custom Integration / Generic Webhook flows that POST to and read responses from arbitrary webhook URLs), and those extracted values are used to configure notification targets and subsequent actions—so remote content can materially influence where and how the agent sends notifications.

Issues (2)

W007
HIGH

Insecure credential handling detected in skill instructions.

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

Audit Metadata
Risk Level
HIGH
Analyzed
Mar 24, 2026, 07:43 AM
Issues
2
Security Audit — snyk — configure-notifications