Security audit

QMT Knowledge Skill

Security checks across malware telemetry and agentic risk

Overview

This is a QMT trading documentation skill that does not execute code itself, but it can help users generate real-trading code and requires careful simulation-first use.

Install only if you want an assistant to help with QMT trading APIs. Treat any generated strategy or passorder code as capable of placing real orders once run inside QMT live mode. Test in simulated signal or simulated broker mode first, verify account, instrument, quantity, price, quickTrade, and risk controls, and redact account details and strategy data before sharing logs.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands

Findings (7)

Description-Behavior Mismatch

High

Confidence: 95% confidence
Finding: This documentation includes extensive live-trading and account-affecting examples such as order placement, repayment, cancellation, and position rebalancing. In the context of a programming-assistant skill, these examples materially increase the chance that an agent or user copies code that triggers real financial actions, causing unauthorized trades or fund movements.

Context-Inappropriate Capability

High

Confidence: 96% confidence
Finding: The examples directly invoke passorder/algo_passorder and related functions for stocks, funds, margin, futures, options, IPO subscription, basket trading, and direct repayment. Even though this is documentation, embedding ready-to-run real-order snippets in an assistant skill creates a dangerous capability expansion from information assistance into operational trade execution.

Missing User Warnings

Medium

Confidence: 92% confidence
Finding: The document gives direct operational guidance for switching a strategy into live trading and states that '实盘' will place actual orders, but it does not provide an explicit safety warning about real financial loss, unintended automated execution, or the need for pre-trade validation. In a skill that helps users generate and run trading strategies, this omission materially increases the chance that a user may execute irreversible real-money trades based on misunderstanding or copied code.

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The guide provides step-by-step instructions for enabling live trading and explicitly notes that '实盘' will place real orders, but it does not present a prominent upfront risk warning immediately before or within the operational steps. In a trading-assistant skill, this omission increases the chance of accidental real-money execution, especially for inexperienced users who may follow UI steps mechanically.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The documentation includes an example for immediate order placement in `after_init` using `passorder(... quickTrade=2 ...)`, which can trigger live trading as soon as a strategy starts. In a trading-assistant skill, code examples are highly likely to be copied directly by users, so presenting immediate execution without a prominent live-trading risk warning increases the chance of accidental real-money orders.

Missing User Warnings

Medium

Confidence: 86% confidence
Finding: The documented `quickTrade` behavior explicitly allows orders to be triggered immediately on model execution, including on historical bars when set to `2`, which materially increases the chance of unintended real trade placement. In a trading-assistant skill, documentation that normalizes immediate execution without a strong, prominent safety warning can mislead users into deploying risky automation in live accounts.

Ssd 3

Medium

Confidence: 90% confidence
Finding: The guide instructs users to send logs to technical staff and names specific log files, but it does not warn that logs may contain account identifiers, strategy code/output, host paths, or trading-related metadata. In a financial/trading context, unsanitized log sharing can expose sensitive operational information that could be misused or mishandled.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.