stablezact-pay@0.73.12
Beautiful and smooth blockchain payment gateway SDK for seamless crypto payments - React & vanilla js
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe credential-exfiltration signal is not substantiated: configured API credentials are sent with payment API requests. However, checkout interactions automatically send merchant and payment context to third-party analytics without an evident consent control, so this is suspicious runtime telemetry rather than a confirmed malicious attack.
Decision evidence
public snapshot- The SDK initializes Mixpanel with a fixed project token and tracks events without a consent or opt-out check in this flow.
- Analytics events include merchant names and payment amounts, with other payment and wallet details tracked by the SDK.
- Opening the checkout modal triggers analytics and initializes Microsoft Clarity.
- The analytics bundle sends events to https://api-js.mixpanel.com.
- Payment API keys and secrets are attached to requests made to the configured payment API URL, consistent with the package's payment SDK purpose.
- The manifest describes a blockchain payment gateway and exposes the checkout bundle as its main entrypoint.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
dist/chunk-DoMj1Wji.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to stablezact-pay@0.73.12.
See all versions of stablezact-pay for other recorded verdicts.
- Review the evidence and your use of stablezact-pay@0.73.12 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.