| Version | Supported |
|---|---|
| 1.0.x | β Active |
| < 1.0 | β Pre-release, no security backports |
Do not open a public GitHub issue for security vulnerabilities.
If you discover a vulnerability β especially one that could leak API keys, drain funds, or compromise a deployed instance β please report it privately:
- π§ Email: moyy@moyvip.com
- π¬ Telegram: @rubuskap (DM only, no group)
Include:
- Description of the issue and its impact
- Steps to reproduce β minimal config / commands
- Affected versions if known
- Your suggested fix if you have one (optional)
- Initial acknowledgement: within 48 hours
- Severity triage: within 7 days
- Patch + disclosure: depends on severity (see below)
- Critical (key leak, RCE, fund drain) β patch in < 7 days, coordinated disclosure
- High (privilege escalation, denial of service) β patch in < 14 days
- Medium / Low β patch in next minor release
These are inherent to the project's design β keep them in mind when deploying:
- All exchange + LLM keys live in
.envβ never commit this file .gitignoreexcludes.envby default- Rotate keys after any suspected leak
- The agent ships in paper mode to prevent accidental real-money trades
- Switching to live mode requires an explicit config flag β review before deploying
- Always run paper for at least 1 week on a new strategy before going live
- News + sentiment plugins fetch external text and pass it to the LLM
- A malicious news article could attempt to override the system prompt
- Mitigations: prompt isolation, rate limits, decision sanity checks (built-in)
- Don't trust LLM output blindly β risk guards must always run after the LLM decision
- Telegram / Discord webhooks can leak trade data if URLs are exposed
- Treat webhook URLs as secrets β store in
.env, never in code
- Run
pip auditperiodically β we don't have automated CVE scanning yet - Pin versions in production (
pip freeze > requirements.lock.txt)
If you deploy trade-agent on a VPS:
- β
Run as non-root user (the systemd unit ships with
User=tradeagent) - β Restrict outbound network to known exchange + LLM endpoints
- β Enable 2FA on every exchange account
- β Use API keys with trading-only scope β no withdrawal, no transfer
- β IP-whitelist API keys at the exchange where possible
- β Set daily loss limits in both the agent config AND the exchange
- β
Monitor
journalctl -u trade-agentβ set up Telegram alerts for crashes
Researchers who responsibly disclose will be credited here (with your permission).
No reports yet.
Thank you for helping keep trade-agent users safe. π