Back to skill

Security audit

Akshare Finance 1.0.0

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward AKShare finance-data helper that fetches public market data and does not show hidden, destructive, credential-seeking, or persistent behavior.

Install this if you are comfortable with a Chinese-language AKShare helper that reaches external public finance-data services. Use a virtual environment and consider pinning dependency versions for reproducible installs; do not treat the returned market data as financial advice.

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

Note
Location
SKILL.md:8
Finding

Unpinned Third-Party Python Dependencies

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:8-15, SKILL.md:27-30, and references/README.md:4-7
Vulnerability Type: Unpinned dependencies and mutable package resolution
Risk Level: Low

Complete Code Snippets

SKILL.md:8-15:

yaml
"requires": { "pip": ["akshare>=1.12", "pandas>=1.5"] },
"install":
  [
    {
      "id": "pip-install",
      "kind": "pip",
      "packages": ["akshare>=1.12", "pandas>=1.5"],

SKILL.md:27-30:

bash
# Install dependencies
pip install akshare pandas

references/README.md:4-7:

bash
pip install akshare pandas

Technical Analysis

The declared dependency constraints specify only minimum versions, while the documented installation commands specify no versions at all. Consequently, installations can resolve to package releases that were not available or reviewed when this Skill was audited.

The package names and documented sources are consistent with the declared financial-data functionality; no dependency confusion, typosquatting, malicious package, or untrusted package index was identified in the reviewed files. The weakness is that dependency resolution remains mutable and lacks integrity verification through exact pins, hashes, or a lock file.

Because imported Python packages execute code in the local interpreter, a compromised upstream release or package-index account could introduce malicious install-time or import-time behavior.

Attack Path

  1. An attacker compromises an upstream dependency release process, maintainer account, or package-distribution channel for akshare, pandas, or a transitive dependency.
  2. The attacker publishes a malicious release that satisfies akshare>=1.12, pandas>=1.5, or the unconstrained installation commands.
  3. A user installs or updates the Skill dependencies without a reviewed lock file or hash verification.
  4. The package manager resolves and installs the malicious r ...[truncated 961 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin every direct dependency to an exact, reviewed version, for example akshare==X.Y.Z and pandas==A.B.C.
  2. Generate and commit a lock file that records all transitive dependencies.
  3. Require cryptographic hashes during installation, such as a hash-locked requirements file used with pip install --require-hashes.
  4. Configure an explicit trusted package index or an internally controlled package mirror rather than relying on ambient package-manager configuration.
  5. Test and review dependency upgrades before updating the pins.
  6. Add automated dependency vulnerability and provenance scanning to the release process.
  7. Update both installation examples so they use the same locked dependency set as the Skill metadata.
  8. Run installation and the Skill scripts under a least-privileged account or isolated environment to limit the impact of a future supply-chain compromise.
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 (5)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

The natural-language content, including the description, headings, and usage notes, is exclusively in Chinese. Under the policy, forcing a specific language without user opt-in can be a locale-policy violation when no alternative language option or justification is provided.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The file’s user-facing natural-language strings and docstrings are written exclusively in Chinese, including descriptions and usage context, with no indication that the user can choose a language or that the skill is intentionally limited to a Chinese-speaking context. This creates a locale/language policy concern because the skill implicitly enforces one language without opt-in or justification.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
96% confidence
Finding

This Python skill includes Chinese-only docstrings and user-facing labels such as "获取宏观经济数据", "CPI通胀", and "PMI采购经理指数" with no indication that the user can choose another language. That creates a natural-language locale policy issue because the skill effectively enforces a specific language without opt-in or documented justification.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

This code performs a remote market-data fetch via the akshare library, which is a network/data-transmission operation covered by the warning requirement for code files. While the function names imply stock retrieval, there is no confirmation prompt, user-facing log/print, or explanatory comment/docstring disclosing that external network access will occur.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
80% confidence
Finding

The call to retrieve the full A-share market snapshot likely contacts an external data source, which falls under network/HTTP operations requiring some form of warning or disclosure in code files. The surrounding code contains no user-facing notice, logging, or explicit documentation that the script will access remote services.

Content

No source excerpt is available for this finding.