@embarkai/ui-kit@0.4.45
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection found risky browser primitives, but they are aligned with a wallet/auth UI kit and are activated by runtime user/application flows rather than npm lifecycle or import-time behavior. No concrete exfiltration, persistence, remote code execution, destructive behavior, or agent control hijack was found.
Decision evidence
public snapshot- dist/iframe/main.js includes bundled wasm-bindgen glue with new Function and a shipped dist/iframe/dkls23_wasm_bg.wasm
- Runtime code fetches authenticated wallet/share data from EmbarkAI/Lumia service APIs and Google/Binance endpoints
- package.json has no install/preinstall/postinstall hooks and no bin entry
- Entrypoints are React/browser bundles: dist/index.js, dist/index.cjs, and dist/iframe/main.js
- No child_process, fs writes, shell execution, persistence hooks, or AI-agent control-surface writes found
- The eval-like new Function is wasm-bindgen import glue, not remote asset decode execution
- Network calls are product-aligned auth, TSS, vault, on-ramp, OAuth, price, explorer, and Google Drive backup flows
- Sensitive localStorage use is wallet/session/passkey/backup state inside browser runtime, not install-time harvesting
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.45.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.45 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.