@embarkai/ui-kit@0.4.94
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe high-risk static match is explained by a bundled local WASM loader and its generated bindings, not a remote decoded payload. The package has no lifecycle hook and the inspected network code is aligned with its stated authentication and account-abstraction functionality.
Decision evidence
public snapshot- The reviewed manifest publishes browser UI entry points and contains no install lifecycle hook.
- The iframe bundle includes a local WebAssembly loader and a WebAssembly binding capable of constructing a Function.
- The flagged stylesheet is minified CSS, not executable code.
- No preinstall, install, postinstall, or prepare script is declared.
- The WebAssembly loader resolves dkls23_wasm_bg.wasm relative to the bundle rather than downloading a remote payload.
- Authenticated vault requests send an encrypted share to the package service as part of an explicit backup feature; no unrelated harvesting or exfiltration was found.
- No child-process execution, environment harvesting, persistence, destructive action, or reviewer-directed text was found in the inspected files.
Source & flagged code
12 flaggedSource fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
dist/iframe/main.jsView on unpkg · L15Package contains a possible secret pattern.
Findings
Affected versions and remediation
This report applies to @embarkai/ui-kit@0.4.94.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.94 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.