registry / @zerohash-sdk/crypto-withdrawals-react / 1.14.0
@zerohash-sdk/crypto-withdrawals-react@1.14.0
A React SDK that enables frontend React applications to seamlessly integrate with the Connect Crypto Withdrawals product.
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe inspected entrypoint uses network access for Zerohash component delivery and failure telemetry. No lifecycle hook, unrelated credential recipient, or concrete attack behavior was found.
Static reason
No blocking static signals were detected.
Trigger
Rendering the exported React component initiates web component loading; telemetry is sent if loading fails.
Impact
The observed network activity supports component delivery and failure monitoring; no malicious behavior or confirmed credential exposure was established.
Mechanism
The component loads an environment-selected script and posts failure details to the corresponding collector endpoint. Its JWT is passed to the web component, while the inspected telemetry payload contains selected claims and app/browser/page metadata.
AI rationale
The inspected entrypoint uses network access for Zerohash component delivery and failure telemetry. No lifecycle hook, unrelated credential recipient, or concrete attack behavior was found.
Evidence
package.jsondist/index.js
Network endpoints5
grafana-faro-collector.dev.0hash.com/collectgrafana-faro-collector.cert.zerohash.com/collectgrafana-faro-collector.zerohash.com/collectgrafana-faro-collector.cert.zerohash.eu/collectgrafana-faro-collector.zerohash.eu/collect
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to a React module entrypoint and shows no install lifecycle hook or runtime self-dependency.
- The entrypoint sends load-failure telemetry to environment-specific Zerohash collector URLs.
- Telemetry contains app, browser, page-origin, and component-load failure details; no credential forwarding or unrelated destination was identified.
- The exported component invokes script loading from React effect setup and supplies its JWT to the loaded web component.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
4 flaggedpackage.jsonView file
1{
"name": "@zerohash-sdk/crypto-withdrawals-react",
"version": "1.14.0",
"private": false,
"type": "module",
"main": "./dist/index.js",
"module": "./dist/index.js",
"types": "./dist/index.d.ts",
"license": "MIT",
"exports": {
"./package.json": "./package.json",
".": {
"types": "./dist/index.d.ts",
"import": "./dist/index.js",
"default": "./dist/index.js"
Low
Suspicious Lifecycle Evidence
The manifest points to a React module entrypoint and shows no install lifecycle hook or runtime self-dependency.
package.jsonView on unpkg · L1dist/index.jsView file
1import { jsxs as U, jsx as d } from "react/jsx-runtime";
import M, { useEffect as A, useState as L, useCallback as j, useRef as D } from "react";
const $ = {
dev: "https://grafana-faro-collector.dev.0hash.com/collect",
cert: "https://grafana-faro-collector.cert.zerohash.com/collect",
prod: "https://grafana-faro-collector.zerohash.com/collect",
"eu-cert": "https://grafana-faro-collector.cert.zerohash.eu/collec
Low
Ai Review Evidence
The entrypoint sends load-failure telemetry to environment-specific Zerohash collector URLs.
dist/index.jsFindings
1 Medium5 Low
MediumNetwork
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
Affected versions and remediation
This report applies to @zerohash-sdk/crypto-withdrawals-react@1.14.0.
See all versions of @zerohash-sdk/crypto-withdrawals-react for other recorded verdicts.
- Review the evidence and your use of @zerohash-sdk/crypto-withdrawals-react@1.14.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.