@embarkai/ui-kit@0.4.95
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe readable source establishes a dynamic code-execution primitive controlled by an opaque bundled binary, so a clean decision is not sufficiently supported. The inspected manifest and loader do not establish malicious installation behavior or a confirmed data-theft chain.
Decision evidence
public snapshot- The iframe bundle exposes new Function with source supplied by WebAssembly memory.
- The iframe loads a bundled WebAssembly module at runtime, leaving executable binary behavior outside readable JavaScript review.
- The manifest has no preinstall, install, or postinstall hook.
- The WebAssembly loader defaults to a package-relative asset rather than a remote URL.
- No child-process invocation or environment-secret transmission was found in the inspected source.
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.95.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.95 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.