@embarkai/ui-kit@0.4.37
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic source inspection found noisy high-risk primitives, but they are package-aligned browser SDK behavior: local bundled WASM glue, explicit iframe wallet/auth flows, and expected service API calls. There is no install-time execution, shell execution, remote payload decode/execute, or unconsented credential/file exfiltration.
Decision evidence
public snapshot- package.json has no preinstall/install/postinstall lifecycle hooks; build scripts are not install-time execution.
- dist/index.js and dist/index.cjs import-time side effect only injects bundled CSS into document.head when in a browser.
- dist/iframe/main.js new Function is wasm-bindgen glue for bundled dkls23_wasm_bg.wasm, not remote decoded payload execution.
- Network calls in dist/index.cjs and dist/iframe/main.js target EmbarkAI auth/TSS/vault/on-ramp APIs, Google Drive APIs, Telegram/Sumsub widgets, Binance price API, and chain explorers for package features.
- No child_process usage found in package source; rm -rf only appears in package.json clean script and embedded package metadata.
- dist/iframe/main.js stores wallet keyshares/auth state in iframe localStorage and gates postMessage actions with SDK channel/session validation.
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.37.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.37 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.