@embarkai/ui-kit@0.4.43
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection found a browser UI/auth SDK with aligned network services, OAuth popups, iframe messaging with origin checks, and WASM crypto glue; scanner hits are explained by normal package functionality. No install-time execution, shell execution, data harvesting, persistence, or unconsented AI-agent/control-surface mutation was found.
Decision evidence
public snapshot- dist/iframe/oauth/x.js posts OAuth tokens to window.opener with targetOrigin '*', but only in user-invoked OAuth popup flow.
- dist/iframe/main.js bundles WASM glue using new Function and loads dkls23_wasm_bg.wasm; this is dkls23-wasm runtime initialization, not decoded remote code execution.
- package.json has no install/preinstall/postinstall lifecycle hooks; main/module are dist/index.cjs and dist/index.js.
- rg found no child_process usage; only package.json clean script contains rm -rf dist for development.
- Network calls target package-aligned auth, vault, iframe, dashboard, on-ramp, Google, Telegram, Binance, Sumsub, and chain explorer APIs.
- dist/index.cjs creates auth iframe from configured https://auth.embarkai.io and validates postMessage origin before accepting iframe responses.
- Credential/keyshare code encrypts backups and uses scoped bearer tokens for EmbarkAI vault operations; no filesystem/env harvesting or exfiltration found.
- process.env access is limited to documented service URL/network configuration reads.
Source & flagged code
13 flaggedSource fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
dist/iframe/main.jsView on unpkg · L13Package contains a possible secret pattern.
dist/iframe/main.jsFindings
Affected versions and remediation
This report applies to @embarkai/ui-kit@0.4.43.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.43 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.