EvoMap Node Integration

• Outcome: Review
• Latest audit: May 29, 2026 at 9:34 PM UTC
• Version:
  1.0.0

Overview

This EvoMap integration is mostly coherent, but it needs review because it tells users to store secrets insecurely and set up an always-on authenticated background heartbeat without enough lifecycle controls.

Install only if you trust EvoMap and want an always-on node integration. Do not put the node secret in MEMORY.md or directly in shell scripts; use environment variables, an OS keychain, or another restricted secret store. Before enabling the LaunchAgent, confirm how to unload it, remove the plist/script/log files, and rotate the node secret if it was exposed.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Rogue Agent: Self-Modification, Session Persistence
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (7)

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The skill instructs users to persist a freshly issued node secret in MEMORY.md, which is likely to be broadly readable within the agent workspace, included in context, or accidentally committed. Storing bearer credentials in a general-purpose memory file materially increases the chance of credential leakage and unauthorized use of the EvoMap account.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The heartbeat instructions create a persistent background process that continuously transmits authenticated requests using a bearer secret embedded in a shell script. This combines credential exposure at rest with silent recurring network egress, which can outlive the user's awareness and be abused if the script or logs are accessed.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The example instructs users to create a shell script, write logs under the user's home directory, and install a LaunchAgent that runs indefinitely at login with KeepAlive enabled, but it does not clearly warn that this establishes persistence and continuous network activity. Even as documentation, this can cause unintended system modification and background execution if copied verbatim.

Session Persistence

Medium

• Category: Rogue Agent

Content

### 2. Set up Heartbeat

```bash
# Create heartbeat script
cat > ~/.openclaw/evomap-heartbeat.sh << 'EOF'
#!/bin/bash
NODE_ID="node_abc123"

• Confidence: 97% confidence
• Finding: Create heartbeat script cat > ~/.openclaw/evomap-heartbeat.sh << 'EOF' #!/bin/bash NODE_ID="node_abc123" NODE_SECRET="your-secret-here" while true; do curl -s -X POST https://evomap.ai/a2a/heartbeat

Session Persistence

Medium

• Category: Rogue Agent

Content

chmod +x ~/.openclaw/evomap-heartbeat.sh

# Create plist
cat > ~/Library/LaunchAgents/ai.openclaw.evomap-heartbeat.plist << 'EOF'
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

• Confidence: 90% confidence
• Finding: plist

Session Persistence

Medium

• Category: Rogue Agent

Content

EOF

# Load it
launchctl load ~/Library/LaunchAgents/ai.openclaw.evomap-heartbeat.plist

# Verify
launchctl list | grep evomap

• Confidence: 96% confidence
• Finding: launchctl load

Session Persistence

Medium

• Category: Rogue Agent

Content

EOF

# Load it
launchctl load ~/Library/LaunchAgents/ai.openclaw.evomap-heartbeat.plist

# Verify
launchctl list | grep evomap

• Confidence: 96% confidence
• Finding: plist

VirusTotal

65/65 vendors flagged this skill as clean.