Back to skill

Security audit

Quant Github Resources

Security checks for vulnerabilities and agentic risk

Overview

This skill is a Chinese-language quant-trading resource list with optional pip install examples; no hidden execution or persistence was found.

Install this as a reference catalog if the Chinese-language quant-trading focus is useful. Do not run the pip block blindly; use a virtual environment or container, verify each package name against the upstream project, and prefer pinned versions from official installation docs.

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
SKILL.md:96
Finding

Unpinned Third-Party Package Installation Guidance

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 96–119
Vulnerability Type: Insecure third-party dependency installation
Risk Level: Medium

Vulnerable Code

bash
# Core backtesting frameworks
pip install backtrader
pip install backtesting
pip install vectorbt

# Machine learning and AI quantitative tools
pip install pybroker
pip install qlib

# Data acquisition
pip install akshare
pip install tushare
pip install yfinance

# Cryptocurrency tools
pip install hummingbot
pip install freqtrade
pip install ccxt

# Portfolio optimization
pip install riskfolio-lib

The comments above are translated from the source; the package-installation commands are reproduced verbatim.

Technical Analysis

The Skill's declared function is to catalog quantitative-finance resources, but its quick-install section recommends installing 13 third-party Python distributions without:

  • Exact version constraints;
  • Cryptographic hashes;
  • A reviewed lockfile;
  • An isolated virtual environment;
  • Explicit package-index selection;
  • Verification that each package name belongs to the referenced project.

Running these commands causes pip to resolve mutable releases from the user's configured package index. Package installation may execute attacker-controlled build or installation logic. A compromised maintainer account, malicious release, dependency-confusion condition, or incorrectly associated package name could therefore result in arbitrary code execution.

The local files do not establish that every package name—particularly qlib—is the official distribution associated with its adjacent listed project. This does not prove that any listed package is malicious, but it makes unconditional installation unsafe without independent verification.

These installations also exceed the minimum privileges necessary for a resource-list Skill. Merely presenting repository links requires neither dependency installation nor execution of third-party package code.

...[truncated 1478 chars]

Remediation
View remediation

Remediation Suggestions

  1. Remove the bulk-install section because dependency installation is not required for the Skill's resource-catalog function.
  2. If installation guidance is retained, clearly mark every command as optional and direct users to each project's reviewed official installation documentation.
  3. Verify that every Python distribution name is owned or endorsed by the corresponding upstream project.
  4. Pin reviewed versions using exact constraints such as package==x.y.z.
  5. Use a lockfile containing hashes for all direct and transitive dependencies, and install with hash verification where practical.
  6. Require installation in a dedicated, non-privileged virtual environment or disposable container.
  7. Do not recommend sudo pip, administrator execution, or installation into the system Python environment.
  8. Specify a trusted package index and warn users that custom or inherited index configuration can introduce dependency-confusion risk.
  9. Review package provenance, release signatures, maintainers, build configuration, and transitive dependencies before updating pinned versions.
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The description is entirely in Chinese and presents the skill as a Chinese-language resource without any indication that users may request another language. Under the language/locale policy, forcing a specific language without user opt-in is a natural-language policy violation unless the regional constraint is explicitly justified.

Content

No source excerpt is available for this finding.