@uipath/rpa-tool@1.201.0
Tool for creating and managing UiPath RPA projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source establishes a real remote execution capability, but it is explicit, registered as a UiPath RPA command, and not automatically activated on installation. Classify it as dangerous dual-use rather than malicious.
Decision evidence
public snapshot- The registered Remote Exec tool accepts an arbitrary shell command for a configured remote robot.
- The command and optional package identifier are forwarded to the remote execution service.
- This is a dangerous remote-code-execution capability, although it is exposed as an explicit product command.
- package.json has no preinstall, install, or postinstall hook.
- The CLI entrypoint runs after explicit command invocation.
- Authenticated API requests derive their base URL from the active UiPath environment; no fixed unofficial credential gateway was found.
Source & flagged code
6 flagged · loading sourcePackage source references child process execution.
dist/packager-tool.jsView on unpkg · L1059Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/packager-tool.jsView on unpkg · L12307Findings
Affected versions and remediation
This report applies to @uipath/rpa-tool@1.201.0.
See all versions of @uipath/rpa-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/rpa-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.