Back to skill

Security audit

IMDb Release Expectation API

Security checks for vulnerabilities and agentic risk

Overview

This skill is a narrow JustOneAPI IMDb lookup helper, but it handles the API token in ways that can expose it in process listings and URL logs.

Review before installing if the JustOneAPI token has paid quota or broad account access. Use a narrowly scoped or revocable token, avoid running the command on shared machines, and rotate the token if logs or process telemetry may have captured it.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
bin/run.mjs:248
Finding

API Token Exposed Through Process Arguments and URL Query Parameters

Content
View full analysis
"}' ``` The token is defined as a query parameter at `bin/run.mjs:19-29`: ```javascript { "defaultValue": null, "description": "User's authentication token.", "enumValues": [], "location": "query", "name": "token", "required": true, "schemaType": "string" }, ``` It is accepted as a command-line argument at `bin/run.mjs:173-176`: ```javascript if (flag === "--token") { parsed.token = value; index += 1; continue; } ``` The credential is inserted into the request parameters at `bin/run.mjs:205-214`: ```javascript function injectToken(operation, params, cliToken) { const tokenParam = operation.parameters.find((parameter) => parameter.name === "token"); if (!tokenParam || params.token !== undefined) { return; } if (!cliToken) { fail("--token is required for this operation.", { operationId: operation.operationId, }); } params.token = cliToken; } ``` Every parameter declared with a query location, including the token, is appended to the URL at `bin/run.mjs:248-256`: ```javascript function applyQueryParams(operation, params, url) { for (const parameter of operation.parameters.filter((item) => item.location === "query")) { const value = params[parameter.name]; if (value === undefined) { continue; } appendValue(url.searchParams, parameter.name, value); } } ``` The resulting URL is sent to the fixed JustOneAPI endpoint at `bin/run.mjs:99-118`: ```javascript const baseUrl = manifest.baseUrl; const url = new URL(operation.path, ensureBaseUr ...[truncated 3482 chars]
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

This code performs an outbound HTTP request after injecting a required token parameter into the query string, but there is no confirmation prompt, user-facing log, or explanatory comment/docstring warning that authentication data will be sent to an external API. Because the file is a code file and handles credentials plus network transmission, it meets the missing-warning criteria.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

Passing an authentication token in the query string is dangerous because query parameters are commonly logged by clients, proxies, monitoring systems, browser history, and server access logs. Even though the base URL uses HTTPS, the token may still be exposed through secondary logging and telemetry, making credential leakage more likely in normal operation.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

This JSON manifest describes the skill generically as calling an endpoint 'with id' but does not define any explicit activation phrases, constraints, or exclusion conditions. In a manifest file, that lack of trigger specificity can make it unclear when the skill should be invoked versus other IMDb-related skills.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.