@embarkai/ui-kit@0.4.41
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 4mo ago · by lpm-firewall-aiScanner findings appear to be false positives from wasm-bindgen glue, CSP allowances, local WASM loading, and legitimate product/API integrations. Static source inspection found no concrete malicious behavior.
Decision evidence
public snapshot- package.json has no install/preinstall/postinstall lifecycle hooks; entries are dist/index.cjs and dist/index.js.
- dist/iframe/main.js WebAssembly load fetches local dkls23_wasm_bg.wasm via import.meta.url, not a remote decoded JS payload.
- dist/iframe/main.js new Function is wasm-bindgen glue (__wbg_newnoargs), not package-authored remote execution.
- Network calls are product-aligned: api.embarkai.io, dashboard.embarkai.io, auth.embarkai.io, Google Drive APIs, Telegram widget, Binance/Etherscan APIs.
- localStorage reads/writes are scoped to auth, passkey, keyshare backup, OAuth state, and wallet session functionality.
- No child_process import, lifecycle execution, credential harvesting loop, persistence mechanism, destructive action, or AI-agent control-surface writes found.
Source & flagged code
14 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.41.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.41 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.