@uipath/integrationservice-tool@1.201.0
Manage Integration Service connectors, connections, and triggers.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious behavior was found, but obfuscated telemetry configuration and incomplete analysis of a subprocess-capable bundled helper prevent a clean decision. There is no install-time execution or proven exfiltration chain.
Decision evidence
public snapshot- The package exposes a command-line executable, so bundled code runs when the user invokes that command.
- The command bundle contains a Base64-decoded telemetry connection string, which obscures its network configuration.
- A bundled browser helper imports child-process support and can launch a command; its static-analysis coverage was incomplete.
- package.json contains no lifecycle scripts or dependencies, so there is no install-time trigger or self-dependency chain.
- The Base64 value is in telemetry initialization and the local default provider is a logger.
- The executable only parses arguments after registering commands; no import-time credential harvesting or file mutation was found.
Source & flagged code
6 flagged · loading sourcePackage source references a known benign dynamic code generation pattern.
dist/index.umd.min-drpc57vn.jsView on unpkg · L1834Findings
Affected versions and remediation
This report applies to @uipath/integrationservice-tool@1.201.0.
See all versions of @uipath/integrationservice-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/integrationservice-tool@1.201.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.