Back to skill

Security audit

Leaptic

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Leaptic device-status API guide, with disclosed credential use and no hidden execution or persistence.

Install only if you are comfortable giving the agent access to your Leaptic App-Key and read-only device snapshot metadata. Prefer platform secret injection, an OS secret store, or a session-only environment variable over a plaintext credentials file, and use only the official regional HTTPS endpoint or a custom endpoint you personally trust.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:61
Finding

App-Key May Be Transmitted to an Unvalidated Configurable Endpoint

Content
View full analysis
``` Example (`base_url` is the full snapshot URL for the user’s region): ```bash curl -sS -X GET "${base_url}" \ -H "App-Key: ${app_key}" ``` ``` The custom endpoint behavior is also explicitly permitted at `SKILL.md:22` and `SKILL.md:46`: ```markdown - **Never** send the App-Key to any host other than the API base in use (official Photon hosts: `photon-prod.leaptic.tech`, `photon-eu.leaptic.tech`, `photon-us.leaptic.tech`, or another `base_url` the user explicitly configured). ``` ```markdown **Recommended:** `~/.config/leaptic/credentials.json` with **both** `base_url` (copy the row for the user’s region) and `app_key`. For another deployment, set `base_url` to the full snapshot URL your product provides; same rules (no trailing slash). ``` ### Technical Analysis Reading the dedicated Leaptic App-Key is necessary for the declared device-snapshot functionality and does not itself exceed the required privilege scope. The Skill limits credential lookup to `LEAPTIC_APP_KEY` and the dedicated `~/.config/leaptic/credentials.json` file, rather than searching unrelated credential locations. However, the destination receiving that credential is selected from `LEAPTIC_BASE_URL` or `base_url` in the credentials file. Although three official hosts are documented, arbitrary custom deployment URLs are also permitted. The instructions ...[truncated 2557 chars]
Remediation
View remediation
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (6)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

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

Content

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

md
| Mechanism | Purpose |
| --------- | ------- |
| `~/.config/leaptic/credentials.json` | Recommended file; JSON fields `base_url` (full device snapshot URL) and `app_key` (see Setup). |
| `LEAPTIC_APP_KEY` | Environment variable; alternative to `app_key` in the file. Matches `metadata.openclaw.primaryEnv` for OpenClaw `skills.entries.leaptic.apiKey` injection. |
| `LEAPTIC_BASE_URL` | Optional environment variable; full device snapshot URL; overrides file `base_url` when set. |

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

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

Content

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

md
| Mechanism | Purpose |
| --------- | ------- |
| `~/.config/leaptic/credentials.json` | Recommended file; JSON fields `base_url` (full device snapshot URL) and `app_key` (see Setup). |
| `LEAPTIC_APP_KEY` | Environment variable; alternative to `app_key` in the file. Matches `metadata.openclaw.primaryEnv` for OpenClaw `skills.entries.leaptic.apiKey` injection. |
| `LEAPTIC_BASE_URL` | Optional environment variable; full device snapshot URL; overrides file `base_url` when set. |

Credential Access

High
Category
Privilege Escalation
Confidence
82% confidence
Finding

The skill recommends storing both base_url and app_key in a plaintext ~/.config/leaptic/credentials.json file. Although it warns about permissions, plaintext credential storage creates a real secret-exposure risk on multi-user systems, compromised endpoints, backups, or when local files are unintentionally indexed or shared.

Content

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

| EU (DE) | https://photon-eu.leaptic.tech/photon-server/api/v1/skill/device/snapshot | | US | https://photon-us.leaptic.tech/photon-server/api/v1/skill/device/snapshot |

Recommended: ~/.config/leaptic/credentials.json with both base_url (copy the row for the user’s region) and app_key. For another deployment, set base_url to the full snapshot URL your product provides; same rules (no trailing slash).

json
{

Credential Access

High
Category
Privilege Escalation
Confidence
77% confidence
Finding

The documented credential resolution flow instructs the skill to read an App-Key from ~/.config/leaptic/credentials.json, reinforcing use of a plaintext local secret store. In a hardware-control skill that accesses device status, compromise of the local host or accidental file disclosure could expose the App-Key and enable unauthorized API access to device metadata.

Content

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

md
Resolve credentials in this order unless the user specifies otherwise:

1. `LEAPTIC_BASE_URL` (if set) else `base_url` from `~/.config/leaptic/credentials.json`. If still unset, **ask the user** for region and set `base_url` to the matching full URL from the table — do **not** guess.
2. `LEAPTIC_APP_KEY` else `app_key` from `~/.config/leaptic/credentials.json`

## Authentication

Credential Access

High
Category
Privilege Escalation
Confidence
77% confidence
Finding

This line explicitly instructs reading app_key from a plaintext credential file if the environment variable is absent. While not malicious, it normalizes insecure secret handling and increases the chance of credential leakage through filesystem compromise, backups, or developer mishandling.

Content

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

md
Resolve credentials in this order unless the user specifies otherwise:

1. `LEAPTIC_BASE_URL` (if set) else `base_url` from `~/.config/leaptic/credentials.json`. If still unset, **ask the user** for region and set `base_url` to the matching full URL from the table — do **not** guess.
2. `LEAPTIC_APP_KEY` else `app_key` from `~/.config/leaptic/credentials.json`

## Authentication

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
80% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

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

md
| `LEAPTIC_APP_KEY` | Environment variable; alternative to `app_key` in the file. Matches `metadata.openclaw.primaryEnv` for OpenClaw `skills.entries.leaptic.apiKey` injection. |
| `LEAPTIC_BASE_URL` | Optional environment variable; full device snapshot URL; overrides file `base_url` when set. |

**Storage:** If you create `credentials.json`, restrict permissions (e.g. `chmod 600`). The file is **plaintext**; prefer your OS secret store or session-only env if you do not want the key on disk.

## Setup