registry / @embarkai/ui-kit / 0.4.123
@embarkai/ui-kit@0.4.123
⚠ Under reviewReact UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 12d ago · by lpm-firewall-aiNo concrete attack was identified: the inspected service requests use configured service URLs, Google OAuth tokens go to Google's Drive API, and the dynamic Function match is Wasm glue. The external auth dependency is unresolved in this snapshot, so its token handling cannot be verified and the package cannot be marked clean.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A runtime API operation that uses the external auth token manager.
Impact
The token handling path cannot be fully assessed from this snapshot; no credential misuse was confirmed.
Mechanism
The bundle imports the token manager and can attach its token to requests sent to the configured service base URL; the dependency implementation was unavailable for review.
AI rationale
No concrete attack was identified: the inspected service requests use configured service URLs, Google OAuth tokens go to Google's Drive API, and the dynamic Function match is Wasm glue. The external auth dependency is unresolved in this snapshot, so its token handling cannot be verified and the package cannot be marked clean.
Evidence
dist/index.jspackage.json
Network endpoints1
api.embarkai.io/tss
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest lists @embarkai/core as a runtime dependency, and the bundle imports its auth token manager; that dependency's implementation is unavailable in this snapshot.
- The bundle allows service URL overrides and can attach the auth token to requests sent to its configured base URL.
- The Google Drive flow obtains a Google OAuth token and sends it to Google's Drive API.
- The iframe's dynamic Function call is in WebAssembly import glue.
Evidence against
- The manifest's scripts are build and development utilities; no install lifecycle hook is declared.
- The inspected code does not establish that the configured service requests send credentials to an unrelated recipient.
Behavioral surface
EnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
14 flaggeddist/iframe/main.jsView file
4507imports.wbg.__wbg_newnoargs_105ed471475aaf50 = function(arg0, arg1) {
L4508: const ret = new Function(getStringFromWasm0(arg0, arg1));
L4509: return ret;
High
336patternName = generic_password
severity = medium
line = 336
Medium
554patternName = generic_password
severity = medium
line = 554
Medium
dist/index.jsView file
Findings
2 Critical3 High12 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.cjs
HighEvaldist/iframe/main.js
HighTrigger Reachable Credential Exfiltrationdist/index.cjs
HighSemantic Analysis Limiteddist/styles.css
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
Affected versions and remediation
This report applies to @embarkai/ui-kit@0.4.123.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.123 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.