T08 · Insecure Dependencies
- Location
SKILL.md:39- Finding
Unpinned Third-Party Package Download and Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a session visualizer, but it automatically starts third-party code and reports sensitive prompts, paths, and commands with weak scoping.
Review before installing. Use only in non-sensitive workspaces unless telemetry is reduced or disabled. Do not expose the local service through a public tunnel without authentication, and prefer a pinned, reviewed AgentCraft version with explicit user consent and redaction for prompts, paths, and commands.
SKILL.md:39Unpinned Third-Party Package Download and Execution
SKILL.md:82Always-On Collection of Sensitive Prompt, Path, and Command Data
SKILL.md:84Unsafe Interpolation of Dynamic Values into Shell and JSON Payloads
SKILL.md:157Unauthenticated Public Exposure of the Local Event Service
The skill does not clearly warn users that it will transmit prompts, working directory, file paths, and shell command data to an event server. The omission is dangerous because users cannot provide informed consent or assess whether the telemetry is appropriate for sensitive environments.
The skill instructs the agent to transmit the full user prompt in mission_start events, which can include secrets, proprietary code, credentials, personal data, or security-sensitive instructions. That data collection is excessive for the stated purpose of game-style visualization and occurs silently in the background.
Including the full user prompt in background event reports sends potentially sensitive user-supplied content to another service without necessity or clear consent. In the context of an agent skill, prompts frequently include confidential instructions, code, credentials, or incident details, making this especially dangerous.
Shell commands often contain secrets, tokens, hostnames, repository paths, and operational details; sending them to another service creates a significant confidentiality risk. Capturing command strings is not clearly justified by the skill's stated visualization purpose and is especially dangerous because the reporting is automatic and silent.
The skill instructs users to expose the local AgentCraft server through a public Cloudflare Tunnel, extending access beyond localhost and potentially allowing external systems to receive or interact with sensitive event data. This substantially increases the attack surface and the sensitivity of all previously collected telemetry.
The remote-sharing section tells users to expose the service publicly but does not warn that this may make locally collected event data available over the internet. Given the sensitivity of prompts, file paths, commands, and cwd telemetry, the lack of warning materially increases the risk of accidental data exposure.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
homepage: "https://getagentcraft.com"
requires:
bins:
- curl
- npx
- head
- date
The manifest presents the skill as visualization/event reporting, but the instructions also tell the agent to automatically deploy and run a local service if it is absent. That hidden expansion from passive reporting to active code execution materially increases risk because it causes installation and runtime behavior not clearly disclosed by the skill description.
The skill launches a package via npx -y @idosal/agentcraft without pinning an exact version, so the executed code can change over time and may be replaced by a compromised or malicious release. Because the skill also instructs automatic background startup, this creates a supply-chain execution path with little user visibility or review.
This event POST sends session and working-directory metadata to a local service automatically and silently in the background. Although localhost transmission is less severe than direct internet exfiltration, it still transfers sensitive context to another process and becomes more dangerous when combined with later tunnel-exposure instructions.
When you begin processing a user prompt:
curl -sf -X POST http://localhost:2468/event \
-H "Content-Type: application/json" \
-d "{\"type\":\"hero_active\",\"sessionId\":\"$AGENTCRAFT_SESSION\",\"client\":\"openclaw\",\"cwd\":\"$PWD\"}" &>/dev/null &
Reporting absolute file paths and file operation details exposes workspace structure, usernames, project names, and sensitive file locations. This exceeds what is obviously necessary for visualization and can leak internal environment details even when file contents are not sent.
File paths and executed shell commands reveal sensitive operational context about the user's environment, repository, infrastructure, and workflows. In a coding-agent setting, this context can materially aid reconnaissance or leak confidential project information even absent direct file-content exfiltration.
The quick-join instructions replicate the same silent background event transmission pattern for other agents, encouraging broader telemetry collection without installation review or meaningful consent. Because this pattern can be shared across agents and later paired with remote exposure, it amplifies the data-leak surface.
AGENTCRAFT_SESSION="openclaw_$(echo -n "$PWD" | md5sum | head -c 12)"
# Report active
curl -sf -X POST http://localhost:2468/event \
-H "Content-Type: application/json" \
-d "{\"type\":\"hero_active\",\"sessionId\":\"$AGENTCRAFT_SESSION\",\"client\":\"openclaw\",\"cwd\":\"$PWD\"}" &>/dev/null &
No suspicious patterns detected.