raspberry-pi-servo

Security checks across malware telemetry and agentic risk

Overview

This is a coherent Raspberry Pi servo-control guide, but users should treat its hardware and boot-configuration steps carefully.

Install only if you are intentionally controlling a servo on Raspberry Pi hardware. Back up boot config before edits, approve any reboot or sudo command, verify the Python package source/version, secure the servo before tests, and stop/disable PWM when finished.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Confidence
85% confidence
Finding
The guide instructs users to disable onboard audio by editing a boot configuration file, but it does not warn that this changes system behavior, can disable the headphone output, and typically requires a reboot to take effect. In a hardware-troubleshooting skill, undocumented system-level changes can cause user harm, confusion, and unintended service disruption even if they are not malicious.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The minimal test performs privileged sysfs writes and starts an infinite motion loop without any stop procedure, timeout, or warning about continuous servo movement. In a servo-control context, this can lead to unexpected physical motion, overheating, mechanical strain, or difficulty stopping the device safely.

VirusTotal

60/60 vendors flagged this skill as clean.

View on VirusTotal