Back to skill

Security audit

Speediance scan PR34 r3

Security checks for vulnerabilities and agentic risk

Overview

The verdict is benign with medium confidence: the scanners report no AIG findings and mostly purpose-aligned behavior, while noting a permissions mismatch and incomplete reference resolution.

The overall verdict is benign, but confidence is medium and the Skillspector scan was partial: some local references could not be resolved. Consider whether the noted permissions mismatch is acceptable for your use before installing.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (7)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 28)May include surrounding context.

md
- "Speediance cloud API (HTTPS) — authentication, workout history, exercise catalog, program creation"
      files.read:
        - "config.json — optional credential/config file (working directory, or your OS user-config dir)"
        - ".env — optional env file in the working directory; only the SPEEDIANCE_EMAIL, SPEEDIANCE_PASSWORD, SPEEDIANCE_REGION and SPEEDIANCE_DEVICE_TYPE keys are read (parsed to a map, never exported into the process environment); the path keys SPEEDIANCE_CONFIG and SPEEDIANCE_TOKEN_CACHE are ignored there"
        - "token cache — cached session token in your OS user-cache dir by default (non-roaming); path overridable via an exported SPEEDIANCE_TOKEN_CACHE, or the token_cache_path key of a config.json given by --config, SPEEDIANCE_CONFIG or the user-config dir (ignored in a working-directory config.json). A legacy .token.json in the working directory is never read; the CLI only warns that it exists."
        - "plan JSON files passed to the push comma

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 54)May include surrounding context.

md
description: "Device type integer — 1 = Gym Monster v1 (default, tested). Gym Monster 2 is untested; try 2 if exercises look wrong."
        required: false
      - name: SPEEDIANCE_CONFIG
        description: "Path to config.json (overrides discovery: working dir, then OS user-config dir). Read from the exported environment only, never from .env"
        required: false
      - name: SPEEDIANCE_TOKEN_CACHE
        description: "Override the token cache file location (default: OS user-cache dir). Read from the exported environment only, never from .env"

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 57)May include surrounding context.

md
description: "Path to config.json (overrides discovery: working dir, then OS user-config dir). Read from the exported environment only, never from .env"
        required: false
      - name: SPEEDIANCE_TOKEN_CACHE
        description: "Override the token cache file location (default: OS user-cache dir). Read from the exported environment only, never from .env"
        required: false
---

Code capability 'shell' detected in internal/auth/tokencache.go but not covered by declared permissions.

High
Category
MCP Least Privilege
Confidence
75% confidence
Finding

The skill uses 'shell' capability that is not covered by the declared MCP 'permissions' list. Review the server's actual authorization policy; runtime permissions are unknown unless separately verified.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · internal/config/config.go (reported line 134)May include surrounding context.

go
if _, exported := exportedOnly(key); exported {
			continue
		}
		warnings = append(warnings, fmt.Sprintf("%s in .env is ignored: path settings must be exported", key))
	}
	return warnings
}

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · internal/config/config.go (reported line 235)May include surrounding context.

go
return nil
	}
	return fmt.Errorf(
		"%w: set %s and %s (exported env vars, or a .env in the working directory), "+
			"or add \"email\"/\"password\" to config.json. config.json is resolved from "+
			"--config / %s, then ./%s, then <user-config-dir>/%s/%s (resolved this run: %s)",
		ErrMissingCredentials, EnvEmail, EnvPassword,

Permission 'file_read' is declared but no corresponding code capability (file_read) was detected.

Low
Category
MCP Least Privilege
Confidence
65% confidence
Finding

Declared permissions with no matching code capability may indicate removed functionality or pre-staging for future abuse.

Content

No source excerpt is available for this finding.