@xrpl-wallet-kit/browser@0.1.13
Browser-ready XRPL Wallet Kit bundle for vanilla JavaScript and legacy HTML sites.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged token flow uses Xumm’s own OAuth endpoints in a browser wallet integration. The scanner’s credential-exfiltration and protestware leads were not confirmed in the inspected source.
Decision evidence
public snapshot- The manifest has no preinstall, install, or postinstall hook; its only script builds the package.
- The module entry re-exports wallet-kit client functionality, matching the package’s stated browser-wallet purpose.
- The flagged Xumm token flow uses Xumm’s own OAuth endpoints and requests the XummPkce scope.
- The bundle’s Xumm userinfo request sends the access token to oauth2.xumm.app, its own OAuth service.
- The static scanner reported credential-exfiltration and protestware patterns in the bundle, but the inspected token flow does not send credentials to an unrelated host.
- The package’s other observed network calls support expected wallet functionality, including XRPL name resolution.
Source & flagged code
6 flaggedSource appears to send environment or credential material to an external endpoint.
dist/xrpl-wallet-kit.iife.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @xrpl-wallet-kit/browser@0.1.13.
See all versions of @xrpl-wallet-kit/browser for other recorded verdicts.
- Review the evidence and your use of @xrpl-wallet-kit/browser@0.1.13 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.