@embarkai/ui-kit@0.6.10
React UI components and hooks for embarkAI authentication and Account Abstraction
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source shows default runtime error-tracking initialization without a disclosure or opt-out found in the package documentation, so this warrants a telemetry warning. The flagged wallet backup and token flows appear consistent with the package’s stated purpose, and the available source does not establish credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Mount the browser Provider with a projectId.
Impact
Error or diagnostic data may be transmitted at runtime; the collected fields and recipient could not be determined from the available source.
Mechanism
The Provider invokes an error-tracking initializer from @embarkai/core; its implementation and telemetry destination are unavailable in this snapshot.
AI rationale
The source shows default runtime error-tracking initialization without a disclosure or opt-out found in the package documentation, so this warrants a telemetry warning. The flagged wallet backup and token flows appear consistent with the package’s stated purpose, and the available source does not establish credential exfiltration.
Evidence
dist/index.js
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- When the browser Provider mounts with a projectId, it automatically calls initSdkErrorTracking().
- The tracking implementation is imported from @embarkai/core/internal/error-tracking, whose source is not present in this package snapshot; the README does not disclose telemetry or an opt-out.
Evidence against
- The package is a React authentication and wallet UI kit, and the inspected backup flow encrypts keyshares before sending them to its vault.
- Iframe messages are checked against the configured iframe origin before they are accepted.
Behavioral surface
EnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
13 flaggeddist/iframe/main.jsView file
20__export(crypto_utils_exports, {
L21: base64ToBytes: () => base64ToBytes,
L22: bytesToBase64: () => bytesToBase64,
...
L169: return {
L170: data: bytesToBase64(new Uint8Array(encryptedData)),
L171: iv: bytesToBase64(iv),
...
L659: const idempotencyKey2 = crypto.randomUUID ? crypto.randomUUID() : `backup-${Date.now()}`;
L660: const response = await fetch(shareUrl("", encryptedShare.ownerAddress), {
L661: method: "PUT",
...
L5369: }
L5370: async upload(fileName, content, usePrivateStorage = true) {
L5371: if (!this.isAuthenticated()) {
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/iframe/main.jsView on unpkg · L206585imports.wbg.__wbg_newnoargs_105ed471475aaf50 = function(arg0, arg1) {
L6586: const ret = new Function(getStringFromWasm0(arg0, arg1));
L6587: return ret;
High
347patternName = generic_password
severity = medium
line = 347
Medium
Secret Pattern
Findings
3 Critical3 High10 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/iframe/main.js
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 Pattern
Affected versions and remediation
This report applies to @embarkai/ui-kit@0.6.10.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.6.10 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.