registry / @embarkai/ui-kit / 0.4.90
@embarkai/ui-kit@0.4.90
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect inspection shows a browser-focused React wallet UI with package-aligned authenticated services. Scanner findings conflate WebAuthn's `eval` field and a bundled Wasm loader with dynamic payload execution.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Application imports and initializes the EmbarkAI UI/wallet flows.
Impact
Expected authentication, MPC wallet, and encrypted-backup functionality; no install-time or covert execution found.
Mechanism
Browser iframe, WebAuthn, packaged Wasm, and authenticated API calls.
AI rationale
Direct inspection shows a browser-focused React wallet UI with package-aligned authenticated services. Scanner findings conflate WebAuthn's `eval` field and a bundled Wasm loader with dynamic payload execution.
Evidence
package.jsondist/index.cjsdist/iframe/main.jsdist/iframe/dkls23_wasm_bg.wasm
Network endpoints4
auth.embarkai.ioapi.embarkai.io/vaultapi.embarkai.io/tssdashboard.embarkai.io/api
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The flagged `eval` is a WebAuthn PRF extension property, not JavaScript evaluation.
- Wasm loader resolves the packaged `dkls23_wasm_bg.wasm` asset; no remote decoded payload execution was found.
- Runtime network calls implement authenticated wallet-backup and UI service operations.
Evidence against
- package.json contains no preinstall, install, or postinstall hook.
- The package exports React UI bundles with sideEffects disabled.
- The iframe checks postMessage sender origin against its configured iframe origin.
- No credential harvesting, shell execution, filesystem access, persistence, or AI-agent configuration mutation found.
Behavioral surface
ChildProcessEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
11 flaggeddist/iframe/main.jsView file
15__export(crypto_utils_exports, {
L16: base64ToBytes: () => base64ToBytes,
L17: bytesToBase64: () => bytesToBase64,
...
L158: return {
L159: data: bytesToBase64(new Uint8Array(encryptedData)),
L160: iv: bytesToBase64(iv),
...
L505: const idempotencyKey = crypto.randomUUID ? crypto.randomUUID() : `backup-${Date.now()}`;
L506: const response = await fetch(`${SHARE_VAULT_URL}/v1/shares/me`, {
L507: method: "PUT",
...
L1902: }
L1903: async upload(fileName, content, usePrivateStorage = true) {
L1904: if (!this.isAuthenticated()) {
Critical
Remote Asset Decode Execute
Source fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
dist/iframe/main.jsView on unpkg · L152747imports.wbg.__wbg_newnoargs_105ed471475aaf50 = function(arg0, arg1) {
L2748: const ret = new Function(getStringFromWasm0(arg0, arg1));
L2749: return ret;
High
336patternName = generic_password
severity = medium
line = 336
matchedText = throw ne...)));
Medium
Secret Pattern
Findings
1 Critical2 High12 Medium5 Low
CriticalRemote Asset Decode Executedist/iframe/main.js
HighChild Process
HighEvaldist/iframe/main.js
MediumSecret Patterndist/iframe/main.js
MediumNetwork
MediumEnvironment Vars
MediumShips Wasm Moduledist/iframe/dkls23_wasm_bg.wasm
MediumStructural Risk Force Deep Review
MediumSecret Patterndist/iframe/main.js
MediumSecret Patterndist/index.js
MediumSecret Patterndist/index.js
MediumSecret Patterndist/index.js
MediumSecret Patterndist/index.cjs
MediumSecret Patterndist/index.cjs
Affected versions and remediation
This report applies to @embarkai/ui-kit@0.4.90.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.90 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.