mediaproc

Security checks across malware telemetry and agentic risk

Overview

This is a coherent media-processing skill, but its setup instructions ask users to run an unpinned remote installer as root.

Install only if you trust the docker-mediaproc project and the host you configure. Do not pipe the GitHub installer directly into `sudo bash`; download and inspect it first, preferably from a pinned release or commit with an integrity check. Use a dedicated SSH key, avoid exposing the mediaproc port broadly, and back up anything important before running uninstall.

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 (3)

Missing User Warnings

Medium
Confidence
98% confidence
Finding
The documentation instructs users to download and immediately execute a remote script as root via `curl ... | sudo bash`, which gives unreviewed network-fetched code full privileged execution. In the context of a media-processing skill that sets up local infrastructure, this is especially dangerous because users are likely to copy-paste it during installation, and any compromise of the upstream script or repository would directly lead to host compromise.

Missing User Warnings

Low
Confidence
88% confidence
Finding
Appending a public key to `~/.mediaproc/authorized_keys` enables SSH access to the containerized environment, but the instructions do not explain that anyone controlling the matching private key will gain access. While this is expected setup behavior for an SSH-based tool, the lack of access-control guidance can lead to accidental exposure or use of the wrong key.

Missing User Warnings

Medium
Confidence
86% confidence
Finding
Describing `mediaproc uninstall` as removing everything without a prominent warning may cause users to destroy configuration, keys, and working data unintentionally. In this skill's context, the tool stores state under `~/.mediaproc/`, so an uninstall likely affects persistent local data and access configuration, making accidental data loss plausible.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal