v1.0.0

Find People (x402)

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 4:57 AM.

Analysis

The skill’s paid people-search function is coherent, but it uses a raw Base wallet private key and an unpinned npm package, so it should be reviewed and isolated before use.

GuidanceUse this only with a dedicated low-balance x402/Base wallet, not a main wallet. Review or pin the npm package before use, restrict any private-key config file permissions, approve each paid lookup, and avoid entering unnecessary sensitive personal details.

Findings (5)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Agentic Supply Chain Vulnerabilities

SeverityHighConfidenceHighStatusConcern

scripts/research.sh

npx -y @itzannetos/x402-tools-claude find-people "$QUERY"

The runtime command invokes an npm package without a pinned version or reviewed package contents in the provided manifest.

User impactThe code that handles the query and exported wallet key can change outside the reviewed artifacts.

RecommendationPin an exact package version or lockfile, publish provenance/source information, and review or vendor the package before passing it credentials.

Tool Misuse and Exploitation

SeverityLowConfidenceHighStatusNote

SKILL.md

Costs $0.15 USDC per request (Base network)

The skill clearly discloses that each request is a paid tool action.

User impactRepeated or accidental invocations can consume wallet funds.

RecommendationConfirm each paid lookup and keep only the amount you are willing to spend in the configured wallet.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityHighConfidenceHighStatusConcern

scripts/research.sh

PRIVATE_KEY=$(jq -r '.private_key' "$CONFIG_FILE" 2>/dev/null || echo "")
export X402_PRIVATE_KEY="$PRIVATE_KEY"

The script reads a raw wallet private key from local config files and exports it into the environment used by the downstream command.

User impactA wallet private key is more powerful than a scoped API token; if mishandled, it can authorize wallet spending beyond a single intended lookup.

RecommendationUse only a dedicated low-balance wallet for this skill, never a primary wallet key, and add explicit credential declaration plus spend/approval limits.

Identity and Privilege Abuse

SeverityMediumConfidenceHighStatusConcern

SKILL.md

echo '{"private_key": "0x..."}' > ~/.x402-config.json

The recommended setup persists the raw private key in a home-directory JSON file.

User impactA plaintext private key file can be exposed through local file access, backups, or overly broad file permissions.

RecommendationPrefer a dedicated low-balance key, store it in a secure secret manager when possible, and if using a file, restrict permissions such as chmod 600.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Insecure Inter-Agent Communication

SeverityLowConfidenceMediumStatusNote

SKILL.md

The API has a 5-minute timeout; comprehensive research may take time

The artifacts indicate API-backed processing, but do not identify the service endpoint or data-handling boundaries.

User impactPerson-search queries may be processed by the service behind the tool rather than staying local.

RecommendationAvoid including unnecessary sensitive details in queries and look for provider, retention, and privacy information before use.