setup-securepay

Warn

Audited by Snyk on Nov 16, 2026

Risk Level: MEDIUM
Full Analysis

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

  • Third-party content exposure detected (medium risk: 0.30). The required workflow involves ingesting webhook callbacks and payment status redirects containing outsider-submitted free text from the SecurePay payment gateway.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

  • Direct money access detected (medium risk: 0.30). The skill's documented task is setting up, building, and debugging SecurePay payment integrations (direct payments, FPX, DuitNow, eMandate direct debit), creating payment requests (POST /v1/payments, Payment Sessions, and v2 payment intents), and handling payment callbacks and status requeries. These operations constitute direct financial execution (charges/purchases/settlement authorization).

For access control, the documentation details authenticating API requests and webhooks (HTTP Basic authentication with UID and auth tokens, client ID/secret for v2, and HMAC-SHA256 checksum verification on callbacks using a Checksum Token). These mechanisms represent independent service-layer authentication and validation enforced by SecurePay's API and gateway infrastructure.

Issues (2)

W011
MEDIUM

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

W009
MEDIUM

Direct money access capability detected (payment gateways, crypto, banking).

Audit Metadata
Risk Level
MEDIUM
Analyzed
Nov 16, 2026, 05:13 AM
Issues
2