ClawHub
Back to skill

Security audit

TradeMemory Protocol

Security checks across malware telemetry and agentic risk

Overview

TradeMemory is a disclosed trading journal and analysis skill, but users should handle its broker credentials and trade data carefully.

Install only if you are comfortable storing trade history locally and, for MT5 sync, providing broker credentials. Prefer demo or read-only investor credentials where possible, keep .env private with restrictive permissions, do not commit it, keep TRADEMEMORY_API on localhost unless you control the endpoint, and manually review any trading or lot-size recommendations before applying them.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Lp3

Medium
Category
MCP Least Privilege
Confidence
90% confidence
Finding
The skill declares environment variables and explicitly describes network activity during installation and optional runtime API communication, but it does not declare corresponding permissions in a structured permissions section. That mismatch can cause the platform or user to underestimate what the skill can access, especially because it handles credentials and may send trade-pattern data to remote endpoints if configured.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The script instructs the user to place MT5 account credentials into a local `.env` file in plaintext and does not clearly warn about the sensitivity of that file or recommend restrictive file permissions. On a shared workstation, backed-up home directory, or repository directory that may later be committed, those credentials could be exposed and allow unauthorized access to the trading account.

Credential Access

High
Category
Privilege Escalation
Content
cd tradememory-protocol

# 3. Configure credentials
cp .env.example .env
# Edit .env with your MT5 login, password, server

# 4. Start the TradeMemory server
Confidence
74% confidence
Finding
The skill instructs users to place MT5 credentials into a local .env file and the metadata declares access to those environment variables. Handling broker login credentials creates a real secret-exposure risk if the file is committed, shared, read by other tools, or insufficiently protected; the danger is elevated by the finance context because exposed credentials could enable account access or sensitive trade-data retrieval.

Credential Access

High
Category
Privilege Escalation
Content
# 3. Configure credentials
cp .env.example .env
# Edit .env with your MT5 login, password, server

# 4. Start the TradeMemory server
python -m src.tradememory.server
Confidence
72% confidence
Finding
This is the same underlying issue manifested on the adjacent line: the setup flow requires editing a .env file with MT5 login details. In a trading skill, plaintext storage of brokerage credentials is especially sensitive because compromise could expose financial data or facilitate unauthorized account interaction through the local MT5 terminal.

Credential Access

High
Category
Privilege Escalation
Content
if [ ! -f ".env" ]; then
    echo "[3/4] Setting up credentials..."
    if [ -f ".env.example" ]; then
        cp .env.example .env
    else
        cat > .env << 'ENVEOF'
# MT5 Account
Confidence
86% confidence
Finding
This logic creates a `.env` file intended to store MT5 login credentials, which constitutes credential collection and local storage. While expected for setup, it is still a real security issue because the script normalizes plaintext secret handling without safeguards, increasing the chance of accidental disclosure through file sharing, backups, or source control.

Credential Access

High
Category
Privilege Escalation
Content
if [ -f ".env.example" ]; then
        cp .env.example .env
    else
        cat > .env << 'ENVEOF'
# MT5 Account
MT5_LOGIN=your_login_here
MT5_PASSWORD=your_password_here
Confidence
92% confidence
Finding
The here-document writes placeholders for `MT5_LOGIN` and `MT5_PASSWORD` into a `.env` file, encouraging users to populate sensitive credentials in plaintext. In the context of a trading tool, compromise of these credentials could expose account data and potentially enable unauthorized account access depending on broker and platform configuration.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.