registry / Telemetry / @ujet/websdk-headless

@ujet/websdk-headless

A prebuilt infrastructure for communicating with your CCaaS servers!

This report shows the evidence for @ujet/websdk-headless@6.32.0. 0 of 17 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 5d ago · by lpm-firewall-ai

The SDK conditionally forwards runtime logs containing the page URL and structured data to a server-configured collector, with no user-facing telemetry choice apparent in the inspected code. Credential masking and the server-controlled trigger reduce the risk, so this is suspicious telemetry rather than clear malicious exfiltration.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

After authentication, when the server response includes `log_proxy_url`; subsequent non-debug logs are queued and forwarded.

Impact

Page URLs or application details present in logs may reach the configured collector without a user-facing telemetry choice in the inspected source.

Mechanism

The SDK builds log records with `location.href` and structured data or messages, then sends the queue through its bridge to the server-configured log proxy. Selected credential fields and common secret patterns are masked.

AI rationale

Evidence

dist/index.mjsdist/index.js

Network endpoints3

websdk.ujet.co/v3/bridge.htmlmain.api.ujet.coserver-provided log_proxy_url (host varies)

Decision evidence

public snapshot

AI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

After authentication, the SDK enables its log proxy handler when the server response contains `log_proxy_url`.
Forwarded log records include the full page URL and structured log data or messages.
The SDK sends queued logs through the bridge, which defaults to `https://websdk.ujet.co/v3/bridge.html`; the log proxy host itself is server-provided.
The SDK masks selected credential-like field names and common token, email, and payment-card patterns before forwarding.

Evidence against

The forwarding requires a server response with `log_proxy_url`; it is not enabled unconditionally by the package code.
The SDK masks several sensitive field names and recognizable secret patterns in logs.
The manifest has no lifecycle scripts, and the package’s apparent purpose is a web communications SDK.

Behavioral surface

Source

EnvironmentVarsEvalFilesystemNetwork

Supply chain

HighEntropyStringsMinified

Source & flagged code

3 flagged

dist/index.jsView file

•Credential-bearing message sent to a fixed external iframe in dist/index.js: "use strict";var Nq=Object.defineProperty;var AC=r=>{throw TypeError(r)};var Lq=(r,e,t)=>e in r?Nq(r,e,{enumerable:!0,configurable:!0,writable:!0,value:t}):r[e]=t;var ye=(r,e,t)=>L... `+nn),Ot&&Ph([Q,Oe,Ve],_n=>{nn=nd(nn,_n," ")}),x&&Nr?x.createHTML(nn):nn},e.setConfig=function(){let vt=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{};Me(vt),zt=!0},e.cl... `)),At=et-1,lt=Math.max(At-3,0),Xr=Math.min(At+3,ct.length);return ie(ct.slice(lt,Xr),function(sn,St,li){return sn[lt+1+li]=St.length<=V?St:St.substr(0,V),sn},{})};p.config.beforeS... `.replace(/\s*\/\/.*$/gm,"").replace(/\n/g,"").trim(),wH=new RegExp(`(?:^${Ws}$)|(?:^${ug}$)`),TH=new RegExp(`^${Ws}$`),EH=new RegExp(`^${ug}$`),Bw=r=>r&&r.exact?wH:new Re

Critical

Hardcoded Runtime Data Exfiltration

Source sends credentials or rich application records to a package-controlled external receiver enabled by default.

dist/index.jsView on unpkg

•stage = ast_semantic_analysis; reason = ast_path_work_budget_exceeded; limitedFiles = 4

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

dist/index.jsView on unpkg

Findings

1 Critical1 High4 Medium6 Low

CriticalHardcoded Runtime Data Exfiltrationdist/index.js

HighSemantic Analysis Limiteddist/index.js

MediumSecret Patterndist/index.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowEval

LowFilesystem

LowHigh Entropy Strings

LowTelemetry

LowUrl Strings

LowNo License

Affected versions and remediation

This report applies to @ujet/websdk-headless@6.32.0.

The versions list below shows the verdict for each recorded version.

Review the evidence and your use of @ujet/websdk-headless@6.32.0 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: 2026-10-30 17:20:49.743Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

17 known versions

6.32.0latestshownSuspiciousTelemetryWarnPublishedOct 30, 2026, 5:13 PM 6.31.1Clean—AllowPublishedOct 28, 2026, 7:38 PM 6.30.0Clean—AllowPublishedOct 26, 2026, 7:10 PM 6.25.0Clean—AllowPublishedOct 14, 2026, 6:04 PM

registry / Telemetry / @ujet/websdk-headless

@ujet/websdk-headless

A prebuilt infrastructure for communicating with your CCaaS servers!

This report shows the evidence for @ujet/websdk-headless@6.32.0. 0 of 17 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 5d ago · by lpm-firewall-ai

Static reason

High-risk behavior combination matched malicious policy.

Trigger

After authentication, when the server response includes `log_proxy_url`; subsequent non-debug logs are queued and forwarded.

Impact

Page URLs or application details present in logs may reach the configured collector without a user-facing telemetry choice in the inspected source.

Mechanism

AI rationale

Evidence

dist/index.mjsdist/index.js

Network endpoints3

websdk.ujet.co/v3/bridge.htmlmain.api.ujet.coserver-provided log_proxy_url (host varies)

Decision evidence

public snapshot

AI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

After authentication, the SDK enables its log proxy handler when the server response contains `log_proxy_url`.
Forwarded log records include the full page URL and structured log data or messages.
The SDK sends queued logs through the bridge, which defaults to `https://websdk.ujet.co/v3/bridge.html`; the log proxy host itself is server-provided.
The SDK masks selected credential-like field names and common token, email, and payment-card patterns before forwarding.

Evidence against

The forwarding requires a server response with `log_proxy_url`; it is not enabled unconditionally by the package code.
The SDK masks several sensitive field names and recognizable secret patterns in logs.
The manifest has no lifecycle scripts, and the package’s apparent purpose is a web communications SDK.

Behavioral surface

Source

EnvironmentVarsEvalFilesystemNetwork

Supply chain

HighEntropyStringsMinified

Source & flagged code

3 flagged

dist/index.jsView file

Critical

Hardcoded Runtime Data Exfiltration

Source sends credentials or rich application records to a package-controlled external receiver enabled by default.

dist/index.jsView on unpkg

•stage = ast_semantic_analysis; reason = ast_path_work_budget_exceeded; limitedFiles = 4

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

dist/index.jsView on unpkg

Findings

1 Critical1 High4 Medium6 Low

CriticalHardcoded Runtime Data Exfiltrationdist/index.js

HighSemantic Analysis Limiteddist/index.js

MediumSecret Patterndist/index.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowEval

LowFilesystem

LowHigh Entropy Strings

LowTelemetry

LowUrl Strings

LowNo License

Affected versions and remediation

This report applies to @ujet/websdk-headless@6.32.0.

The versions list below shows the verdict for each recorded version.

Review the evidence and your use of @ujet/websdk-headless@6.32.0 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: 2026-10-30 17:20:49.743Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

17 known versions