T09 · Insecure Skill Coding Practices
- Location
scripts/move_x_minus150.py:5- Finding
Robot Motion Executes Automatically When Modules Are Imported or Discovered
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a real robot-control skill with a clear purpose, but it includes live-motion scripts and tests that can move connected hardware without adequate safety gates.
Review before installing on any machine that can reach a real robot. Treat the examples and tests as live hardware programs, remove or gate module-scope motion scripts, require explicit operator confirmation and independent safety interlocks, validate motion/output bounds, fix reset_alarm semantics, and pin reviewed dependency versions before use.
scripts/move_x_minus150.py:5Robot Motion Executes Automatically When Modules Are Imported or Discovered
tm_robot.py:349Motion and I/O APIs Forward Unvalidated Safety-Critical Parameters
tm_robot.py:476Alarm Reset API Does Not Reset Alarms and Can Mislead Safety-Critical Callers
manifest.json:12Third-Party Robot Control Dependency Is Unpinned and Unverified
The README documents live robot motion and stop commands (move_joints_zero, zero, stop) and I/O control capabilities without an explicit safety warning about physical movement, pinch/crush hazards, workspace clearance, E-stop readiness, or safe commissioning procedures. In a network-connected industrial robot context, users may run examples directly against production hardware, which can result in unintended motion, collisions, or actuation that may injure people or damage equipment.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Token
Yes
string
API access token
ActionTarget
Yes
int
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Token
Yes
string
API access token
ActionTarget
Yes
int
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Token
Yes
string
API access token
ActionTarget
Yes
int
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Token
Yes
string
API access token
ActionTarget
Yes
int
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Token
Yes
string
API access token
ActionTarget
Yes
int
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Token
Yes
string
API access token
ActionTarget
Yes
int
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Token
Yes
string
API access token
ActionTarget
Yes
int
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Token
Yes
string
API access token
ActionTarget
Yes
int
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
projects. To run the Warp node at its best efficiency, mind each of the following as listed:
1.
No warning while the project is running.
2.
Do not insert the dongle key.
3.
This example issues real robot motion commands immediately without any explicit safety interlock, workspace check, or user confirmation. In an industrial robotics context, executing movement from sample code can cause collision, equipment damage, or operator injury if run against a live robot.
The cartesian motion example modifies the current pose and moves the robot without warning the user or validating that the vertical path is clear. Even a simple Z-axis offset can be hazardous on a live manipulator if tooling, fixtures, or people are present in the workspace.
The test runner automatically calls movement routines as part of a general 'run all tests' flow, which increases the chance that a user executes live robot motion unintentionally. Auto-running physical actuation from example/test code is especially dangerous because users may expect tests to be non-destructive and safe.
This demo initiates real robot motion commands, including homing and movement to a target joint configuration, without any explicit safety interlock, simulation-only mode, operator acknowledgment, or warning that physical movement will occur. In a robotics context, executing movement from an example script can cause unexpected motion, collision, or injury if a user runs it on connected hardware assuming it is a harmless demo.
The full demo combines connection, monitoring, robot motion, and digital output control in one workflow, increasing the chance that a user runs it end-to-end on a live system without appreciating that it performs hazardous physical actions. Combining multiple actuator-affecting behaviors without a safety gate materially raises operational risk, especially in industrial robotics where motion and output changes can interact with tooling and nearby equipment.
The script executes reset_alarm() immediately after the stop routine with no user confirmation, hazard check, or verification of why the alarm was raised. On a physical robot, clearing alarms without operator review can re-enable motion readiness or mask unsafe states, creating a real safety risk if faults are bypassed during testing.
This script connects to a physical robot and immediately issues movement commands, including joint, linear, circular, and homing motions, without any operator acknowledgment, safety interlock, dry-run mode, or environment check. In a robotics context, automatic motion can cause collisions, equipment damage, or human injury if the workspace is not cleared or the robot state is unexpected.
The script directly invokes a physical robot arc motion command as soon as the code reaches that branch, with no operator confirmation, interlock check, simulation mode, or workspace safety validation. In a robotics context this is dangerous because unexpected motion can cause collision, equipment damage, or human injury if the robot is connected to a live system.
The linear move command is issued immediately to a hard-coded target pose without any confirmation or runtime safety validation. Because this controls real hardware over the network, an unintended run could move the robot into fixtures, people, or unreachable/collision-prone positions.
Even the 'return to safe position' joint move is still an immediate live motion command and assumes the named pose is actually safe in the current environment. If the robot's current tooling, fixtures, or surroundings differ from expectations, this motion can itself be hazardous.
The script initiates physical robot motion automatically via asyncio.run(test()) and calls move_joint(...) without any operator confirmation, interlock check, or pre-actuation safety gate. In a robotics context, unsolicited motion is inherently dangerous because it can cause collisions, equipment damage, or human injury if the workspace is occupied or the robot state is not as expected.
This script issues real robot motion commands directly after connecting and reading pose, with no explicit operator confirmation, interlock check, simulation/dry-run mode, workspace validation, or emergency-stop readiness prompt. In a robotics context, moving +100mm on X based solely on current pose can cause collisions, fixture damage, or injury if the robot is not in a verified safe state.
The joint motion interface allows immediate physical robot movement with no confirmation, interlock check, workspace validation, or user-facing safety warning. In a collaborative robot setting, exposing direct motion primitives without pre-execution safeguards can lead to unintended motion, collisions, equipment damage, or operator injury if invoked by mistake or through higher-level automation.
The linear, absolute, relative, and circular motion methods perform safety-critical path motion without validating target coordinates, confirming operator intent, or checking whether the current robot state permits safe execution. This is especially dangerous because path-based motion can sweep through occupied space, so even a valid endpoint may still create collisions or human-safety hazards.
The entire checklist and release guidance are written in Chinese, and there is no indication that users may choose another language or that the skill is intentionally limited to a Chinese-only audience. Under the stated policy, forcing a specific language without opt-in is a natural-language policy violation.