supabase-query

HIGH W007: Insecure credential handling detected in skill instructions.

• Insecure credential handling detected (high risk: 1.00). The prompt hardcodes Supabase bearer tokens and example curl commands that embed those tokens verbatim, so the agent would need to handle and output secret values directly.

CRITICAL E006: Malicious code pattern detected in skill scripts.

• Malicious code pattern detected (high risk: 1.00). The skill intentionally embeds valid Supabase Management API tokens and project refs and documents how to run arbitrary SQL (including DDL) against multiple projects—this provides direct, account-level remote access suitable for data exfiltration, unauthorized schema/data modification, and persistent backdoor-style access.

HIGH W008: Secret detected in skill content (API keys, tokens, passwords).

• Secret detected (high risk: 1.00). The prompt contains two literal, high-entropy bearer tokens that are directly usable credentials:
• sbp_64d15ce2602aced67109aa4324130f7eafa389f6 (Hermetic Account token)
• sbp_7d35e363115a3952471185b627bbf7971be75151 (Docti Account token)

Both appear in Authorization headers and the Tokens table and have the form of real service tokens (high entropy, not placeholders). Project refs like yjpiapfrayxaavhccher, tnrtofrdfzjbrlqorgvl, etc. are identifiers (not secrets) and are not flagged. No other private keys or high-entropy secrets are present.

These tokens should be treated as compromised in this document — rotate/revoke and remove from source control or docs.