Back to skill

Security audit

okx-sentiment-tracker

Security checks for vulnerabilities and agentic risk

Overview

The skill mostly matches its OKX news and sentiment purpose, but it asks users to configure live exchange credentials in a risky way and includes a workflow that can access account positions and balances.

Install only if you are comfortable using OKX live API credentials with this CLI. Prefer a dedicated least-privilege read-only API key, avoid entering secrets directly in shell commands, consider isolated installation instead of a global npm install, and review any workflow that asks to inspect positions or balances before allowing account access.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (2)

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:56
Finding

Live API credentials exposed through command-line arguments

Content
View full analysis
SK= PP= name=live ``` ### Technical Analysis The documented profile-creation command instructs users to substitute a live API key, secret, and passphrase directly into command-line arguments. Depending on the operating system and shell configuration, those values may be exposed through: - Shell history files - Process-listing and process-monitoring tools - Terminal session recordings - Diagnostic or support logs - Audit frameworks that record executed commands The use of a live profile increases the sensitivity of this exposure. Although the Skill describes its news commands as read-only, the effective permissions associated with the supplied API credentials are determined by the credential configuration and the external CLI. The audited files do not establish that those credentials are technically restricted to read-only news access. ### Attack Path 1. The user follows the documented setup procedure and replaces the placeholders with live credentials. 2. The shell records the complete command in its history, or the operating system temporarily exposes the arguments through process metadata. 3. A local attacker, malicious process, monitoring service, or person with access to captured terminal logs retrieves the API key, secret, and passphrase. 4. The attacker attempts to authenticate to OKX using the recovered credentials. 5. The resulting access is bounded by the permissions, account restrictions, IP allowlist, and other controls configured for those credentials. ### Impact Assessment Successful exploitation may disclose all three authentication components needed by the external CLI. An attacker could obtain whatever API privileges were assigned to the exposed credentials. The precise scope cannot be ...[truncated 392 chars]
Remediation
View remediation

T08 · Insecure Dependencies

Note
Location
SKILL.md:44
Finding

Globally installed third-party CLI introduces supply-chain and lifecycle-script risk

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
Findings (8)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger description is broad enough to match generic requests such as 'latest news', 'market update', or macro commentary, which can cause this skill to activate outside its narrow intended scope. Misrouting can lead the agent to use the wrong tool, unnecessarily require credentials, or pull from a narrower or less appropriate data source than the user intended. The skill is read-only, so impact is limited, but overbroad invocation still creates reliability and scope-control risk.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill explicitly instructs the agent to fall back to unrestricted web search when OKX data is sparse. That expands the trust boundary from a constrained vendor API to arbitrary external sites, creating prompt-injection, data provenance, and policy-scope risks that are not otherwise present in a read-only API workflow. In this context the danger is moderated because the action is still read-oriented, but it is a real security and integrity issue.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The instruction says language is inferred from the user's message and maps automatically to --lang zh-CN or --lang en-US. This imposes a locale choice without explicit user opt-in, which can violate language/locale choice policy when a user may prefer a different output language than the one inferred from their prompt.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger description contains many broad, everyday phrases such as 'latest news', 'market update', 'daily briefing', and 'read more' that can match common user requests outside the intended scope. Because this skill requires API credentials and accesses external market/news functionality, overbroad invocation increases the chance the agent will select it unintentionally, causing unnecessary credential use, incorrect tool routing, or unintended external data access.

Content

No source excerpt is available for this finding.

Ae4

Medium
Category
analysis-evasion
Confidence
80% confidence
Finding

Suspicious Unicode normalization or mixed-script content

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The document states that all news and sentiment commands are read-only, but later instructs the agent to access account positions and balances and to provide position-specific trading suggestions via other skills. This mismatch can mislead routing, trust, and consent boundaries, increasing the chance that a user or agent invokes sensitive account-access workflows under the false assumption that the skill remains purely read-only.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This workflow expands a news/sentiment skill into portfolio inspection and individualized position-impact analysis, including balance and positions retrieval plus actionable suggestions. That creates an over-broad capability path where a user asking about macro/news can be steered into disclosure of sensitive financial data and personalized trading guidance without a scope match or clear consent checkpoint.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
94% confidence
Finding

The line specifies a user request example in Chinese alongside English, implying special handling for a specific language/locale without stating whether other languages are equally supported or whether this is a China-specific workflow. Under the policy rule, forcing or privileging a specific language without user opt-in can be a natural-language policy issue.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.