Security audit

tqsdk

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only TqSdk helper skill whose trading examples are disclosed and aligned with its purpose, but users should be careful with live-account credentials and real order code.

Install only if you want help with TqSdk trading or market-data code. Before adapting examples, keep real brokerage and Quick credentials out of source files, prefer simulation or backtest first, and confirm the account type before running any code that can place or cancel orders.

A.I.G

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

SkillSpector

Vulnerability Patterns

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
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (10)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The reference shows plaintext credentials directly in sample code without any warning or safer alternative, which can normalize unsafe secret-handling and lead users to paste real trading passwords into source files, notebooks, or shared snippets. In a trading/account skill, this is more dangerous than a generic example because the credentials grant access to financial accounts and may expose users to unauthorized trading or account compromise if copied into logs, repos, or screenshots.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The multi-account example includes a real-account object instantiated with plaintext credentials, which is especially risky because it demonstrates direct use of live brokerage access in code and may encourage users to store production secrets alongside automation logic. In the context of a trading skill, this increases the chance of credential leakage and unauthorized access to real funds, positions, and order placement capability.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The file provides direct order placement and cancellation examples for a trading SDK without an explicit warning that these actions can place or cancel live market orders. In a trading-focused skill, users may copy examples verbatim into production or real accounts, so the omission increases the chance of unintended financial transactions rather than code execution compromise.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 82% confidence
Finding: This reference presents error messages in Chinese as canonical examples, which can impose a specific language/locale on users without any opt-in or explanation. Because the document otherwise uses English, these untranslated strings may conflict with a language-choice policy unless the locale dependency is documented.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The example hardcodes Chinese placeholder strings for account and password, which imposes a specific language/locale in the skill content. The file does not indicate that Chinese is required for a region-specific reason or offer an alternative language-neutral example.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 93% confidence
Finding: This example again uses Chinese-only placeholder credentials in natural-language-visible code, reinforcing a fixed locale choice without user opt-in. Nothing in the document explains that the skill is limited to Chinese users or provides alternate wording.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The code sample continues to require Chinese-language placeholders, which is a natural-language locale constraint present in the file. Because the document is otherwise English and does not justify the locale restriction, this is a policy-style language choice issue.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The final example repeats the same Chinese-only placeholder strings, creating a consistent language-specific requirement in the skill text. The file does not offer users a language choice or explain why this locale-specific format is necessary.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 83% confidence
Finding: The example uses fixed Chinese strings for account and password placeholders ("快期账户", "账户密码") in code, which imposes a specific language/locale in instructional content without opt-in or explanation. This can conflict with language/locale neutrality policies when the document is otherwise general-purpose reference material.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 83% confidence
Finding: This example again uses Chinese-only credential placeholders in general documentation, reinforcing a specific locale without documenting that it is optional or region-specific. The issue is natural-language policy related rather than a code defect.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.