Vx Troubleshooting

Security checks across malware telemetry and agentic risk

Overview

This is a legitimate vx troubleshooting guide, but it tells agents to run remote installer commands and delete local vx state without enough safeguards.

Review before installing or using this skill. It does not show hidden exfiltration or unrelated malicious behavior, but users should require explicit approval before any installer runs, prefer reviewed and pinned installation steps, and treat deletion of ~/.vx or vx.lock as destructive recovery actions only after confirming backups and consequences.

SkillSpector

By NVIDIA

Vulnerability Patterns

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

Findings (2)

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The guide instructs users to delete `vx.lock` without an explicit warning that this is destructive and may discard reproducibility state or alter dependency resolution. In an agent context, terse destructive advice can be executed mechanically, causing unintended project state changes or hard-to-debug environment drift.

Missing User Warnings

High

Confidence: 99% confidence
Finding: The guide recommends `curl ... | bash` and PowerShell `irm ... | iex`, which execute remote code directly from the network without verification, review, or pinning. This is dangerous because any compromise of the hosting source, network path, or referenced branch can immediately lead to arbitrary code execution on the user's machine.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal