registry / @uipath/integrationservice-tool / 1.202.1
@uipath/integrationservice-tool@1.202.1
Manage Integration Service connectors, connections, and triggers.
AI Security Review
scanned 28d ago · by lpm-firewall-aiInspection shows a normal UiPath CLI: no lifecycle hooks, browser opening only after a dynamic import, and OIDC authorities forced to HTTPS with a UiPath cloud default. Process execution is limited to fixed OS helpers used by that CLI flow.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the integrationservice-tool CLI or imports the module; nothing runs on npm install.
Impact
No unconsented credential theft, remote payload execution, persistence, or consumer-project mutation was found.
Mechanism
Commands talk to a configured HTTPS UiPath host and may open a browser through a dynamic import of the vendored open helper.
AI rationale
Inspection shows a normal UiPath CLI: no lifecycle hooks, browser opening only after a dynamic import, and OIDC authorities forced to HTTPS with a UiPath cloud default. Process execution is limited to fixed OS helpers used by that CLI flow.
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a module entry and the integrationservice-tool CLI bin and declares no install lifecycle scripts.
- The browser helper is loaded only by a dynamic import that then opens a caller-supplied URL.
- Default authentication authority is https://cloud.uipath.com, and non-HTTPS authorities are rejected before token exchange.
- dist/index-sby22td6.js is the vendored open/powershell helper used for that browser launch, not an install hook.
Evidence against
- child_process calls are fixed OS utilities such as reg query and browser launchers, invoked from CLI code rather than package install.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
6 flagged · loading sourcedist/tool-1bgza1fn.jsView file
•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration.
dist/tool-1bgza1fn.js:
async writeFile(filePath, data) {
await fs.writeFile(filePath, data);
await fs.writeFile(lockFile, ownerId, { flag: "wx" });
await this.writeFile(destEntry, content);
"authorization",
await fs2.writeFile(path2, "");
headerParameters["Authorization"] = `Bearer ${tokenString}`;
headerParameters["Authorization"] = `Bearer ${tokenString}`;
High
Credential Redirect Persistence
Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/tool-1bgza1fn.jsView on unpkg4362var telemetryInstanceSlot = singleton("TelemetryService");
L4363: var DEFAULT_AI_CONNECTION_STRING = atob("[redacted]...
L4364: function getGlobalTelemetryInstance() {
High
Base64 Obscured Url
Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-1bgza1fn.jsView on unpkg · L436212547var UIPATH_HOME_DIR2 = ".uipath";
var AUTH_FILENAME = ".auth";
var DEFAULT_BASE_URL = "https://cloud.uipath.com";
var DEFAULT_AUTH_TIMEOUT_M
Findings
3 High3 Medium6 Low
HighCredential Redirect Persistencedist/tool-1bgza1fn.js
HighBase64 Obscured Urldist/tool-1bgza1fn.js
HighSemantic Analysis Limiteddist/index-sby22td6.js
MediumNetwork
MediumEnvironment Vars
MediumStripped Provenance Metadatadist/tool-1bgza1fn.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/tool-1bgza1fn.js
Affected versions and remediation
This report applies to @uipath/integrationservice-tool@1.202.1.
See all versions of @uipath/integrationservice-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/integrationservice-tool@1.202.1 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.