@embarkai/ui-kit@0.4.46
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection shows scanner hits are explained by expected browser SDK behavior: fetches to product and integration APIs, wasm-bindgen glue, base64 conversion, and localStorage state. There is no install/import-time malicious behavior, exfiltration pattern, persistence, destructive action, or agent-control hijack.
Decision evidence
public snapshot- package.json has no preinstall/install/postinstall hooks and only exposes dist entrypoints
- Network calls in dist/index.cjs and dist/iframe/main.js are runtime SDK/API operations for auth, wallet, share vault, Google Drive backup, Binance/on-ramp, and project metadata
- dist/iframe/main.js ships dkls23 wasm glue; new Function appears in wasm-bindgen/lodash-style glue, not remote decoded payload execution
- atob/base64 use in dist/iframe/main.js handles binary/key/signature conversion; no decoded string is fed to eval/Function
- No child_process, fs writes, persistence hooks, or AI-agent control-surface mutations found
- localStorage usage stores package-aligned session, authorization, UI, and keyshare backup state in browser runtime
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.46.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.46 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.