registry / stablezact-pay / 0.68.0
stablezact-pay@0.68.0
Beautiful and smooth blockchain payment gateway SDK for seamless crypto payments - React & vanilla js
AI Security Review
scanned 4mo ago · by lpm-firewall-aiScanner credential-exfiltration hints map to SDK-authenticated requests using caller-provided merchant credentials and package-aligned payment endpoints, not source-confirmed secret harvesting. With no lifecycle hook, filesystem access, shell execution, persistence, or unconsented agent mutation, this should be marked clean.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Application imports and invokes SDK components or payment/API helpers at runtime.
Impact
No unauthorized install-time execution, credential/file exfiltration, persistence, or control-surface hijack found.
Mechanism
merchant-configured payment API requests and browser wallet/payment flows
AI rationale
Scanner credential-exfiltration hints map to SDK-authenticated requests using caller-provided merchant credentials and package-aligned payment endpoints, not source-confirmed secret harvesting. With no lifecycle hook, filesystem access, shell execution, persistence, or unconsented agent mutation, this should be marked clean.
Evidence
package.jsonREADME.mddist/index.esm.jsdist/index-CW1p6ar4.jsdist/CoinleyPayment-C6ChHSdL.jsdist/QRCodePayment-C50CNuFu.js
Network endpoints6
api.coinley.comapi.coinley.iopayment.coinley.iowww.clarity.ms/tag/pro-api.coinmarketcap.comapi-js.mixpanel.com
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Hardcoded CoinMarketCap key in dist/index-CW1p6ar4.js for exchange-rate fetches.
- Payment APIs forward merchant-supplied apiKey/apiSecret/publicKey as auth headers to configured baseURL.
Evidence against
- package.json has no npm lifecycle hooks or bin entries.
- dist/index.esm.js only re-exports SDK modules; payment UI is lazy-loaded at app runtime.
- dist/CoinleyPayment-C6ChHSdL.js network calls are payment, bridge, wallet, token, and analytics flows aligned with checkout SDK behavior.
- No source evidence of child_process execution, filesystem writes, credential harvesting from env/files, persistence, or AI-agent control-surface mutation.
- process.env assignment appears to be a browser polyfill shim, not env collection.
- Agent discovery code only adds/removes coinley meta tags in document head when components mount.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flaggeddist/CoinleyPayment-C6ChHSdL.jsView file
6import ReactDOM, { createPortal } from "react-dom";
L7: import { useConnect, useAccount, useSwitchChain, useSendTransaction, useWaitForTransactionReceipt, WagmiProvider, useDisconnect } from "wagmi";
L8: import { QueryClientProvider, QueryClient } from "@tanstack/react-query";
...
L155: eip712Meta: {
L156: ...args.gasPerPubdata ? { gasPerPubdata: toHex(args.gasPerPubdata) } : { gasPerPubdata: toHex(gasPerPubdataDefault) },
L157: ...args.paymaster && args.paymasterInput ? {
...
L359: default: {
L360: http: ["https://api.mainnet.abs.xyz"],
L361: webSocket: ["wss://api.mainnet.abs.xyz/ws"]
...
L2097: if (!response.ok) {
L2098: const error = await response.json().catch(() => ({}));
L2099: throw new Error(error.error || `HTTP ${response.status}`);
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/CoinleyPayment-C6ChHSdL.jsView on unpkg · L66Trigger-reachable chain: manifest.module -> dist/index.esm.js -> dist/index-CW1p6ar4.js -> dist/CoinleyPayment-C6ChHSdL.js
L6: import ReactDOM, { createPortal } from "react-dom";
L7: import { useConnect, useAccount, useSwitchChain, useSendTransaction, useWaitForTransactionReceipt, WagmiProvider, useDisconnect } from "wagmi";
L8: import { QueryClientProvider, QueryClient } from "@tanstack/react-query";
...
L155: eip712Meta: {
L156: ...args.gasPerPubdata ? { gasPerPubdata: toHex(args.gasPerPubdata) } : { gasPerPubdata: toHex(gasPerPubdataDefault) },
L157: ...args.paymaster && args.paymasterInput ? {
...
L359: default: {
L360: http: ["https://api.mainnet.abs.xyz"],
L361: webSocket: ["wss://api.mainnet.abs.xyz/ws"]
...
L2097: if (!response.ok) {
L2098: const error = await response.json().catch
Findings
2 Critical1 High3 Medium6 Low
CriticalCredential Exfiltrationdist/CoinleyPayment-C6ChHSdL.js
CriticalTrigger Reachable Dangerous Capabilitydist/CoinleyPayment-C6ChHSdL.js
HighOversized Source Filedist/coinley-vanilla.min.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowObfuscated
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to stablezact-pay@0.68.0.
See all versions of stablezact-pay for other recorded verdicts.
- Review the evidence and your use of stablezact-pay@0.68.0 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.