STM32 CubeMX

Security checks across malware telemetry and agentic risk

Overview

This looks like a normal STM32CubeMX helper; the main caution is that it includes a clean-build delete command that should only run in the intended project folder.

Install only if you want an agent to help edit and regenerate STM32CubeMX project files. Before running its shell snippets, verify `PROJECT_DIR`, `IOC_FILE`, `SCRIPT_FILE`, and `CUBEMX` point to the intended local project and trusted STMicroelectronics tooling, and keep the project in version control or backed up because code generation and clean-build steps can overwrite or remove build artifacts.

SkillSpector

By NVIDIA

Vulnerability Patterns

Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (1)

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The skill includes an unconditional destructive deletion command as part of its normal workflow without any warning, confirmation, or validation of the target path. While presented as routine cleanup, this is dangerous in an agent context because variables like PROJECT_DIR or the working directory may be mis-set, causing unintended data loss outside the intended build tree.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal