IMDb Contribution Questions API

Security checks across malware telemetry and agentic risk

Overview

No malicious behavior is indicated, but the skill appears to send an API token in the request URL, which users should treat as a credential-exposure risk.

Install only if you trust the API provider and can use a limited, revokable token. Avoid sharing logs, traces, or full request URLs from this skill, and rotate the token if a URL containing it is exposed.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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
98% confidence
Finding
The API authentication token is defined and sent as a query parameter, which places the secret in the URL. URLs are commonly logged by proxies, servers, browser history, monitoring systems, and exception traces, so this increases the chance of credential exposure even when HTTPS is used. In this skill context, the code also injects the token automatically and provides no warning, so accidental leakage is more likely.

Missing User Warnings

Medium
Confidence
96% confidence
Finding
The API requires the authentication token to be sent as a query parameter, which is commonly exposed in logs, browser history, intermediary proxies, monitoring tools, and referrer headers. Even if HTTPS is used, placing secrets in the URL materially increases the chance of credential leakage and unauthorized reuse of the token.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal