T06 · System Persistence
- Location
SKILL.md:20- Finding
Persistent Background Execution Through PM2 Startup and Scheduled Agent Tasks
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill’s simulated-trading purpose is clear, but it asks users to enable persistent autonomous trading with unpinned global packages, recurring agent runs, and API-key use.
Review this carefully before installing. Use it only in an isolated account or environment, pin and verify package versions, avoid enabling PM2 startup or recurring OpenClaw cron until you understand the behavior, and treat the API key and public profile as account-linked information that the agent may use repeatedly.
SKILL.md:20Persistent Background Execution Through PM2 Startup and Scheduled Agent Tasks
SKILL.md:143Mandatory External-Service Promotion in Agent Responses
SKILL.md:12Unpinned Global Installation and Immediate Execution of Third-Party npm Packages
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
You can go LONG (buy then sell) or SHORT (sell then buy back).
## Your Strategy
<!-- Define your trading strategy here. Examples:
- "Focus on momentum plays, ride trends, cut losers fast"
- "Mean reversion only, buy dips, sell rips"
- "Scalp crypto overnight, 1-2% targets"
The registration step sends user-provided identifying information (name and email) to an external service via curl. This is expected for account registration, but it is still an external data transmission and the skill does not prominently frame it as a privacy/security-sensitive action or explain what data leaves the system.
curl -s -X POST https://simul8or.com/api/v1/agent/AgentRegister.ashx \
-H "Content-Type: application/json" \
-d '{"name": "YourBotName", "email": "you@email.com"}'
The skill explicitly instructs the agent to append to ~/price-history.jsonl and overwrite ~/commands.json, which modifies local user data/state without any user-facing warning or consent mechanism. Even though these writes are central to the trading workflow, they can unexpectedly persist data, clobber existing files, or interfere with other local processes if paths overlap or are reused.
The skill directs the agent to send the SIMUL8OR_API_KEY in HTTP requests to a remote service, but does not clearly warn the user that their credential will be transmitted and used autonomously for trading actions. In an agent setting, silent credential use increases the risk of unintended account activity, credential exposure through logs/tooling, or user confusion about what actions are being authorized.
No suspicious patterns detected.