T09 · Insecure Skill Coding Practices
- Location
config.json:10- Finding
Plaintext Longport Broker Credentials Stored in a Tracked Configuration File
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a real automated trading package, but it includes high-impact broker trading authority plus exposed credentials and a hard-coded Feishu notification recipient that users should review before installing.
Do not use this with a real brokerage account until the bundled credentials are removed and rotated, Feishu recipients are fully user-configured, dependency versions are pinned, and live order execution is gated by explicit paper-trading tests, position limits, and a kill switch. Treat the existing package as requiring manual security review before installation.
config.json:10Plaintext Longport Broker Credentials Stored in a Tracked Configuration File
qqq_monitor_push.py:23Hard-Coded Feishu Application Secret and Fixed Message Recipient
SKILL.md:32Unpinned Third-Party Python Dependency Installation
Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.
"""获取应用身份访问令牌"""
url = f"{BASE_URL}/auth/v3/tenant_access_token/internal"
payload = {"app_id": APP_ID, "app_secret": APP_SECRET}
response = httpx.post(url, json=payload, timeout=10)
result = response.json()
if result.get("code") == 0:
return result.get("tenant_access_token")
Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.
"msg_type": "interactive",
"content": content
}
response = httpx.post(url, headers=headers, json=payload, timeout=10)
result = response.json()
return result
Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.
"app_id": FEISHU_APP_ID,
"app_secret": FEISHU_APP_SECRET
}
response = requests.post(url, json=payload)
data = response.json()
if data.get("code") == 0:
return data.get("tenant_access_token")
Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.
"content": json.dumps(message_content) # content 字段需要是 JSON 字符串
}
response = requests.post(url, headers=headers, json=payload)
result = response.json()
if result.get("code") == 0:
The README markets fully automated stock trading, stop-loss/take-profit, and 5-minute monitoring without any visible warning about financial risk, market volatility, execution failure, or the possibility of losing user funds. In the context of a retail-investor trading skill, this omission can mislead users into overtrusting the automation and deploying it on live assets without understanding the risks.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
5. 创建后获得三个密钥:
- `App Key`
- `App Secret`
- `Access Token`
### 1.3 配置环境变量
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
5. 创建后获得三个密钥:
- `App Key`
- `App Secret`
- `Access Token`
### 1.3 配置环境变量
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
source ~/.zshrc
**方法 3: 使用 .env 文件**
在项目目录创建 `.env` 文件:
LONGPORT_APP_KEY=your_app_key_here
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
source ~/.zshrc
**方法 3: 使用 .env 文件**
在项目目录创建 `.env` 文件:
LONGPORT_APP_KEY=your_app_key_here
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.
The documentation advertises an automated Longbridge quant trading system with live HK/US trading, 5-minute monitoring, stop-loss/take-profit handling, Feishu notifications, and performance tracking, while the analyzed behavior is reported as materially different or incomplete. In a financial automation context, this mismatch is dangerous because users may trust the skill to place, limit, or exit trades safely when those controls may not exist, causing financial loss, unintended orders, or unsafe deployment with real credentials.