T08 · Insecure Dependencies
- Location
SKILL.md:36- Finding
Unpinned Remote Package Execution Through CLI Fallback
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill fits its escrow-submission purpose, but it needs review because it handles wallet signing credentials and suggests unsafe package and private-key setup patterns.
Install only if you are comfortable letting the agent run git-escrows commands that may use a wallet private key and submit blockchain escrow actions. Use a dedicated low-value wallet, avoid pasting private keys into command lines or chat, prefer a pinned and preinstalled git-escrows version, and confirm any fulfillment or collection action before it is run.
SKILL.md:36Unpinned Remote Package Execution Through CLI Fallback
SKILL.md:43Wallet Private Key Exposed Through Command-Line Arguments
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
name: fulfill-git-escrow
description: Fulfill a git escrow bounty by writing a solution or submitting an existing one. Use when the user wants to solve a test suite challenge, write code to pass tests, and claim a token reward. Requires the git-escrows CLI (npm i -g git-escrows).
compatibility: Requires git-escrows CLI, git, a configured .env with PRIVATE_KEY, and network access to an Ethereum RPC endpoint.
allowed-tools: Bash Read Write Edit Glob Grep
metadata:
author: arkhai-io
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
name: fulfill-git-escrow
description: Fulfill a git escrow bounty by writing a solution or submitting an existing one. Use when the user wants to solve a test suite challenge, write code to pass tests, and claim a token reward. Requires the git-escrows CLI (npm i -g git-escrows).
compatibility: Requires git-escrows CLI, git, a configured .env with PRIVATE_KEY, and network access to an Ethereum RPC endpoint.
allowed-tools: Bash Read Write Edit Glob Grep
metadata:
author: arkhai-io
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
name: fulfill-git-escrow
description: Fulfill a git escrow bounty by writing a solution or submitting an existing one. Use when the user wants to solve a test suite challenge, write code to pass tests, and claim a token reward. Requires the git-escrows CLI (npm i -g git-escrows).
compatibility: Requires git-escrows CLI, git, a configured .env with PRIVATE_KEY, and network access to an Ethereum RPC endpoint.
allowed-tools: Bash Read Write Edit Glob Grep
metadata:
author: arkhai-io
The example command shows a raw private key argument (--privateKey "0x...") with no warning not to paste real secrets into terminals, chat, shell history, or logs. This is especially risky because users may imitate examples literally, exposing a wallet key that can lead to irreversible compromise of blockchain assets and identity.
The skill explicitly depends on a .env containing PRIVATE_KEY and instructs the agent to perform blockchain-related submission actions, but it provides no warning about sensitive credential handling or transaction risk. In this context, omission of safety guidance increases the chance of accidental secret exposure, misuse of signing authority, or unintended financial actions.
The skill recommends running npx git-escrows as a fallback without pinning a specific package version. That can execute whatever version is currently resolved from the registry at runtime, creating a supply-chain risk, especially because this skill also expects local secrets and blockchain-signing capability in the same environment.