registry / @embarkai/ui-kit / 0.4.96
@embarkai/ui-kit@0.4.96
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a concrete cross-origin authorization weakness in a wallet-capable iframe, but the package does not show install-time malware, payload staging, or deliberate exfiltration. The package should be warned pending a fix that authenticates and binds origins to project authorization.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user loads the EmbarkAI wallet iframe from a malicious HTTPS origin.
Impact
An attacker may impersonate an authorized application and induce wallet signing or access wallet-related responses.
Mechanism
Overbroad postMessage origin trust and authorization not bound to origin.
AI rationale
This is a concrete cross-origin authorization weakness in a wallet-capable iframe, but the package does not show install-time malware, payload staging, or deliberate exfiltration. The package should be warned pending a fix that authenticates and binds origins to project authorization.
Evidence
dist/iframe/main.js
Network endpoints1
api.embarkai.io
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for warning
- The iframe accepts an initial SDK_AUTH message from any HTTPS origin.
- That message creates a channel token and adds the arbitrary origin to the allowed-origin set.
- Transaction signing then relies on the caller-controlled channel, user ID, and project ID; authorization is not bound to the message origin.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- The reported dynamic Function calls are WebAssembly glue and bundled lodash code, not a remote decoded payload.
- The bundled CSS is presentation-only, and no filesystem or child-process behavior was found.
Behavioral surface
ChildProcessEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
12 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
Medium
Secret Pattern
Package contains a possible secret pattern.
Findings
1 Critical3 High12 Medium5 Low
CriticalRemote Asset Decode Executedist/iframe/main.js
HighChild Process
HighEvaldist/iframe/main.js
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
MediumSecret Patterndist/index.js
MediumSecret Pattern
Affected versions and remediation
This report applies to @embarkai/ui-kit@0.4.96.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.96 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.