@embarkai/ui-kit@0.6.11
React UI components and hooks for embarkAI authentication and Account Abstraction
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged credential-exfiltration claim is not supported: the observed backup traffic goes to EmbarkAI's own service and uploads an encrypted envelope. The package can still create that server-managed wallet backup automatically after sign-in, so warn users about the sensitive default behavior.
Decision evidence
public snapshot- After sign-in, the UI flow calls `syncServerBackupAfterLogin` automatically.
- That sync calls `ensureServerBackup` with the user's access token.
- Iframe authentication allows Basic backup creation; the creation path proceeds unless `allowCreate` is false.
- The Basic backup path encrypts the keyshare into an envelope, then PUTs that envelope to the vault with a bearer resource token. The vault is hosted at `api.embarkai.io`.
- The backup flow sends data to the package's own EmbarkAI service, consistent with its wallet and MPC key-management purpose.
- The uploaded keyshare is encrypted into an envelope; the source does not show credentials being sent to an unrelated host.
- The manifest declares no lifecycle scripts, and the automatic backup is tied to sign-in rather than package installation.
Source & flagged code
13 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/iframe/main.jsView on unpkg · L20Findings
Affected versions and remediation
This report applies to @embarkai/ui-kit@0.6.11.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.6.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.