@zerohash-sdk/csp-crypto-withdrawals-react@1.15.11
A React SDK that enables frontend React applications to seamlessly integrate with the Connect CSP Crypto Withdrawals product.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe component sends undisclosed runtime telemetry on widget load failures, including the page origin and JWT-derived metadata. The ZeroHash endpoints and failure-only trigger fit the package’s purpose, so this is suspicious telemetry rather than a clear attack.
Decision evidence
public snapshot- When the remote widget script fails to load or times out, the component reports the failure.
- The report is sent as a JSON POST with keepalive enabled.
- The report includes the browser user agent and page origin.
- JWT claims are decoded into participant and platform metadata included in the report.
- The default collector is a ZeroHash Grafana Faro endpoint; the public component props do not document telemetry or an opt-out.
- The network report is triggered by a widget loading failure, not merely by importing the package.
- The package’s purpose is to load ZeroHash’s hosted crypto withdrawals component, and its default CDN and collector hosts are ZeroHash domains.
Source & flagged code
6 flaggedWhen the remote widget script fails to load or times out, the component reports the failure.
dist/index.jsView on unpkg · L121The report is sent as a JSON POST with keepalive enabled.
dist/index.jsView on unpkg · L78The report includes the browser user agent and page origin.
dist/index.jsView on unpkg · L57Findings
Affected versions and remediation
This report applies to @zerohash-sdk/csp-crypto-withdrawals-react@1.15.11.
See all versions of @zerohash-sdk/csp-crypto-withdrawals-react for other recorded verdicts.
- Review the evidence and your use of @zerohash-sdk/csp-crypto-withdrawals-react@1.15.11 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.