Back to skill

Security audit

Eth Strategy

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed ETH/USDT technical-analysis tool that fetches public market data and prints trading levels, with no evidence of hidden execution, account access, or trade placement.

Install this only in an isolated environment with pinned dependency versions if possible. Treat the generated trading levels as informational analysis, not financial advice; the skill does not place trades, but following its output could still cause financial loss.

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

T08 · Insecure Dependencies

Warning
Location
requirements.txt:1
Finding

Unpinned Third-Party Dependencies

Content
View full analysis

Vulnerability Details

File Location: requirements.txt, lines 1–4
Vulnerability Type: T08: Insecure Dependencies
Risk Level: Medium

Vulnerable Code

text
pandas
pandas-ta
ccxt
numpy

Technical Analysis

All third-party packages are specified without exact versions or integrity hashes. Consequently, each installation may resolve to a different package release than the versions originally reviewed and tested. The dependency list also provides no cryptographic mechanism for verifying that downloaded artifacts are the approved artifacts.

This creates supply-chain exposure if a dependency's distribution account or release process is compromised. It also allows an unreviewed future release to be installed automatically. The audit found no evidence that the listed package names are typosquatted or currently malicious; the issue is the absence of deterministic and integrity-verified dependency resolution.

Attack Path

  1. An attacker compromises the release channel, maintainer account, or distribution artifact of a listed dependency.
  2. The attacker publishes a malicious release under the legitimate package name.
  3. A user installs the project dependencies from the unconstrained requirements.txt.
  4. The package manager resolves the affected dependency to the malicious release.
  5. Malicious package code executes during installation or when imported by main.py.

Impact Assessment

Malicious dependency code could run with the privileges of the user installing or invoking the skill. It could access files, environment variables, network resources, and credentials available to that user, modify local data, or execute additional processes. The scope would be limited by the operating-system permissions and sandbox controls applied to the installation and runtime environment.

Remediation
View remediation

Remediation Suggestions

  1. Pin every direct dependency to an exact, reviewed version using ==.
  2. Generate a lock file that captures reviewed transitive dependency versions.
  3. Record cryptographic hashes for all resolved artifacts and install with hash verification, such as pip install --require-hashes -r requirements.txt.
  4. Retrieve packages only from explicitly configured, trusted registries over TLS.
  5. Integrate dependency vulnerability, provenance, and package-name checks into CI.
  6. Review and test dependency updates before deliberately regenerating the lock file and hashes.
  7. Install and execute the skill in a least-privileged, isolated environment with restricted filesystem and network access.
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (10)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill explicitly provides trading direction, entry, stop-loss, and take-profit guidance, which can materially influence financial decisions, yet it does not warn users about market risk, possible losses, or that outputs are informational only. In this context, omission of risk disclosure increases the chance that users over-trust the recommendation and suffer preventable financial harm.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

This skill emits concrete trading signals with entry, stop, and take-profit levels but provides no warning that the output is speculative and can cause financial loss if followed. In the context of an agent skill intended for end users, that omission increases the chance users treat the output as authoritative financial advice and act without understanding risk.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The module docstring specifies the skill behavior entirely in Chinese and frames the output contract in that language, with no indication that users may choose another language. For a general-purpose trading-analysis script, this is a language-policy issue because it imposes a specific locale without opt-in or documented regional justification.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

The core description uses a single language and does not indicate that the skill is intentionally limited to Chinese-speaking users or provide an opt-in language choice. This can violate language/locale policy when a skill implicitly forces one language without notice.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
97% confidence
Finding

The dependency list does not pin a specific pandas version, which makes builds non-reproducible and can cause the environment to resolve to an unexpected or newly compromised release. While this file alone does not prove exploitation, unpinned packages increase supply-chain risk and make it harder to verify whether vulnerable versions are installed.

Content

Scanner excerpt · requirements.txt (reported line 1)May include surrounding context.

text
pandas
pandas-ta
ccxt
numpy

Unverifiable Dependency: pandas has 1 known advisory(ies) (CVE-2020-13091 (** DISPUTED ** pandas through 1.0.3 can unserialize and execute commands from an)), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
88% confidence
Finding

Pandas has known advisories, and because no version is pinned, it is impossible to determine from this manifest whether the deployed environment is affected. In this trading-analysis skill, the risk is still limited by the manifest alone, but the ambiguity prevents reliable vulnerability assessment and could permit installation of an affected release.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
97% confidence
Finding

The pandas-ta package is unpinned, so installs may pull different versions over time, including releases with breaking changes or security issues. This creates a software supply-chain weakness because the exact dependency state cannot be audited or reproduced reliably.

Content

Scanner excerpt · requirements.txt (reported line 2)May include surrounding context.

text
pandas
pandas-ta
ccxt
numpy

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
97% confidence
Finding

The ccxt dependency is not version-pinned, allowing package resolution to vary between installations. Because ccxt interacts with exchange APIs and potentially sensitive trading workflows, unexpected dependency changes could affect integrity, reliability, or expose the system to supply-chain compromise.

Content

Scanner excerpt · requirements.txt (reported line 3)May include surrounding context.

text
pandas
pandas-ta
ccxt
numpy

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
97% confidence
Finding

The numpy package is unpinned, which weakens reproducibility and leaves open the possibility of resolving to a vulnerable or malicious release. Even widely used packages are part of the supply chain, so version ambiguity is a real security hygiene issue.

Content

Scanner excerpt · requirements.txt (reported line 4)May include surrounding context.

text
pandas
pandas-ta
ccxt
numpy

Unverifiable Dependency: numpy has 16 known advisory(ies) (CVE-2014-1859 (Numpy arbitrary file write via symlink attack); CVE-2021-41495 (NumPy NULL Pointer Dereference); CVE-2021-33430 (NumPy Buffer Overflow (Disputed)) +13 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
90% confidence
Finding

NumPy has multiple historical advisories, and the unpinned requirement means the installed version cannot be verified as safe. Although this manifest does not directly exploit anything, leaving the version unspecified increases the chance that an affected build could be installed in some environments.

Content

No source excerpt is available for this finding.