Back to skill

Security audit

DataXAPI Competitors

Security checks for vulnerabilities and agentic risk

Overview

The skill provides a clearly scoped competitor-post lookup with disclosed charges and spending limits.

Check the planned maximum charge before running and use a budget-limited API key. Prefer a reviewed, pinned CLI version. Requests go through DataXAPI; this review covers the skill instructions, not the external CLI or service implementation.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
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 (1)

MCP server referenced without pinned version: 'npx dataxapi'.

Medium
Category
MCP Rug Pull
Confidence
94% confidence
Finding

The skill recommends executing an unpinned npm package through npx dataxapi or installing it globally without a version, allowing the code executed to change independently of the reviewed skill. A compromised package release could execute with the agent's permissions and potentially access DATAXAPI_API_KEY, local files, or other credentials. Although the finding incorrectly describes this CLI as an MCP server, the underlying supply-chain risk is real; spending caps and instructions to treat returned content as untrusted do not constrain malicious CLI code.

Content

No source excerpt is available for this finding.