registry / @connect-xyz/withdraw-react / 0.54.5
@connect-xyz/withdraw-react@0.54.5
A React SDK that enables frontend React applications to seamlessly integrate with the Connect Withdraw product.
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected network activity is consistent with a withdrawal UI wrapper: it loads the Connect SDK and reports failure metadata. No concrete malicious behavior was identified.
Static reason
No blocking static signals were detected.
Trigger
The consumer renders the component; telemetry is sent only when the remote component fails to load.
Impact
No confirmed harmful impact or attack surface was established in the inspected code.
Mechanism
The wrapper loads the Connect SDK URL for the selected environment and posts limited failure metadata to its collector URL.
AI rationale
The manifest has no install hook, and the inspected network activity is consistent with a withdrawal UI wrapper: it loads the Connect SDK and reports failure metadata. No concrete malicious behavior was identified.
Evidence
dist/index.js
Network endpoints7
sdk.sandbox.connect.xyz/withdraw-web/index.jssdk.connect.xyz/withdraw-web/index.jsgrafana-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 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes dist/index.js and lists only React peer dependencies, with no install lifecycle hook.
- dist/index.js sends failure telemetry containing app, page-origin, browser, and script-load error metadata to a selected collector URL.
- The component loads the Connect withdrawal web component from the package’s Connect SDK URLs and passes through the caller-provided JWT.
Evidence against
- Inspected network behavior aligns with the React withdrawal SDK: telemetry is limited to load failures, and the loaded component uses Connect-owned SDK hosts.
- No credential harvesting, unrelated recipient, install-time mutation, or other confirmed attack behavior was identified.
Behavioral surface
Network
UrlStrings
Source & flagged code
4 flaggedpackage.jsonView file
5"type": "module",
"main": "./dist/index.js",
"module": "./dist/index.js",
"types": "./dist/index.d.ts",
"license": "MIT",
"exports": {
"./package.json": "./package.json",
".": {
"types": "./dist
Low
Suspicious Lifecycle Evidence
package.json exposes dist/index.js and lists only React peer dependencies, with no install lifecycle hook.
package.jsonView on unpkg · L518"files": [
"dist",
"!**/*.tsbuildinfo"
],
"nx": {
"name": "withdraw-react"
},
"peerDependencies": {
"react": ">=18.0.0",
"react-dom": ">=18.0.0"
}
}
Low
Suspicious Lifecycle Evidence
package.json exposes dist/index.js and lists only React peer dependencies, with no install lifecycle hook.
package.jsonView on unpkg · L18dist/index.jsView file
183if (!e || typeof fetch > "u") return;
let { sessionId: r, payload: i } = v(t, n);
try {
fetch(e, {
method: "POST",
headers: {
"Content-Type": "application/json",
"x-faro-session-id": r
},
body: JSON.stringify(i),
keepalive: !0
}).catch(() => void 0);
} catch {}
}, b = (e) => {
let { webComponentTag: t, appName: n, appVersion: r, scriptUrls: i, fallbackScriptUrls: a, collectorUrls: o, env: s, jwt: c, timeo
Findings
1 Medium5 Low
MediumNetwork
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
Affected versions and remediation
This report applies to @connect-xyz/withdraw-react@0.54.5.
See all versions of @connect-xyz/withdraw-react for other recorded verdicts.
- Review the evidence and your use of @connect-xyz/withdraw-react@0.54.5 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.