Back to skill

Security audit

bus-servo-arm-calibrate

Security checks for vulnerabilities and agentic risk

Overview

This is a Markdown-only calibration guide whose local code-edit advice is expected for saving robotic arm settings, with no hidden execution, data access, persistence, or network behavior found.

Installers should treat this as a practical hardware-calibration guide. Before following it, keep the robot workspace clear, review any edits to tune_grasp.py or constants files, and prefer version control or a backup before applying in-place changes.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The example demonstrates sed -i modifying tune_grasp.py in place without a warning, backup step, or safer alternative. While the command is not inherently malicious and operates on a hard-coded local file, in-place edits can accidentally corrupt code, make changes hard to audit or revert, and encourage unsafe copy-paste behavior by users.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
75% confidence
Finding

This markdown skill instructs the user to write slot parameters into a constants file and store everything in code, which affects user files. The document does not include an explicit warning that following these steps will modify local code/configuration and should be reviewed or backed up.

Content

No source excerpt is available for this finding.