setup-fasspay
Audited by Snyk on Nov 16, 2026
HIGH W008: Secret detected in skill content (API keys, tokens, passwords).
- Secret detected (high risk: 1.00). The only candidate is in
references/account-setup.md(lines 55-56): a UAT Merchant ID (800010000000179) and a UAT secret key (0EvpYKg0I9iS80ef3WhMHqtLUBigyZxVhXtCKYqYCVs=).
The secret is a high-entropy, base64-looking literal, so it is not a placeholder, and it is a real HMAC signing key rather than a simple setup password. The document says these are shared public sandbox credentials embedded in the official Fasspay WooCommerce plugin source and identical for every developer. The instructions to flag actual, usable credentials still apply to the literal value. It is a concrete, usable credential for the UAT environment, even though that environment is a sandbox. I am flagging it, with the caveat that its severity is low because the document describes it as publicly published sandbox material.
fasspay-api.md repeats the UAT MID (line 280) but does not give the secret there. A MID is an identifier, not a secret.
Nothing else is a secret. The remaining content consists of env var names, placeholders like <MID> and <token>, example emails, and public API documentation. The tempPin mentions are instructions only.
Issues (1)
Secret detected in skill content (API keys, tokens, passwords).