Minimax Vision Search

Security checks across malware telemetry and agentic risk

Overview

This skill is a disclosed MiniMax image-analysis and web-search helper, with expected privacy and API-key handling cautions but no artifact-backed malicious behavior.

Install only if you trust MiniMax and the uvx package source. Avoid sending confidential images or search prompts unless provider processing is acceptable, delete locally saved Telegram images when no longer needed, and prefer careful secret storage over broadly persisting the API key in shell startup files.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Lp3

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding
The skill advertises and instructs use of capabilities that imply environment variable access, shell execution, and network access, but it does not explicitly declare corresponding permissions. This creates a transparency and policy-enforcement gap: users or orchestrators may approve the skill under incomplete assumptions, while the skill can still drive external requests and consume secrets such as API credentials in practice.

Missing User Warnings

Medium
Confidence
84% confidence
Finding
The README states that Telegram images are automatically saved to a local directory, but it does not clearly warn users about the privacy and data-retention implications of storing potentially sensitive images on disk. This can lead to unintentional retention of personal or confidential content, especially on shared systems or environments where users assume images are processed transiently.

Missing User Warnings

Medium
Confidence
87% confidence
Finding
The setup guide instructs users to export and persist an API key in shell configuration without warning about secret handling, shell history exposure, multi-user system risks, or safer alternatives. While common, this can lead to credential leakage through dotfiles, screenshots, shared environments, backups, or accidental commits.

Missing User Warnings

Medium
Confidence
88% confidence
Finding
The troubleshooting guidance instructs users to append an API key export directly into their shell profile, creating long-lived credential persistence without warning about leakage through dotfile backups, shared accounts, or accidental disclosure. While this is common convenience guidance, it increases the exposure window of a sensitive secret and is unsafe documentation practice.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal