setup-lekirpay

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 (low risk: 0.10). The required workflow only reads official LekirPay docs and API schemas, but at runtime the status requery (GET /api/payments/{payment_id}/status) returns payer-supplied name and item fields for a specific payment, and the callback body carries the same payer-controlled fields.

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

  • Direct money access detected (medium risk: 0.30). The skill is mainly developer guidance for building a LekirPay checkout integration, which is excluded as implementation guidance. However, its Core Workflow directs the agent to create live payments server-side through the Send Payment API (POST /api/payments/payment/secure) and redirect customers to the returned payment_url. That creates a real payment request, akin to a real bill or invoice, which is an indirect operation. No direct transfer, charge, refund, or settlement is documented. The skill also does not document a service-enforced access control for that route, but indirect operations do not require one. Because the evidence is ambiguous between excluded development guidance and an operational payment-creation workflow, the recall-first override applies and the answer is medium.

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