registry / @embarkai/ui-kit / 0.4.89
@embarkai/ui-kit@0.4.89
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe static alert conflates normal browser WebAssembly glue and an explicit OAuth-gated backup feature with malicious execution. Direct inspection found no lifecycle execution or concrete malicious chain.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Application runtime when the consumer uses wallet backup or Google Drive features.
Impact
Optional transmission of user-selected encrypted wallet backup data to configured storage services.
Mechanism
OAuth-gated wallet-backup and local bundled-Wasm initialization.
AI rationale
The static alert conflates normal browser WebAssembly glue and an explicit OAuth-gated backup feature with malicious execution. Direct inspection found no lifecycle execution or concrete malicious chain.
Evidence
package.jsonREADME.mddist/index.cjsdist/iframe/main.jsdist/iframe/dkls23_wasm_bg.wasm
Network endpoints4
apis.google.com/js/api.jsaccounts.google.com/gsi/clientwww.googleapis.com/upload/drive/v3/files?uploadType=multipartapi.embarkai.io/vault
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Runtime Google Drive integration loads Google API scripts and uploads only after OAuth consent.
- Wasm-bindgen glue exposes Function construction, but initializes from the bundled relative wasm asset.
Evidence against
- package.json has no preinstall, install, postinstall, or prepare hook.
- Package is a React authentication/MPC wallet UI kit; README matches the shipped functionality.
- Google upload requires an authenticated OAuth token and calls a consent prompt.
- No source evidence of filesystem harvesting, child-process execution, stealth persistence, or AI-agent control-surface writes.
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.89.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.89 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.