T08 · Insecure Dependencies
- Location
SKILL.md:26- Finding
Unpinned Third-Party Package Executed Through npx
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is aligned with managing domains, but it enables real purchases and DNS changes without enough guardrails for confirmation, credential handling, or dependency pinning.
Review this skill before installing. Use a pinned, reviewed version of the MCP package if possible, keep the DomainForAgents API key in a secret store or environment variable, avoid printing API keys or claim codes in chat logs, and require explicit confirmation before any domain purchase, renewal, payment action, or DNS write.
SKILL.md:26Unpinned Third-Party Package Executed Through npx
The skill instructs users to run an MCP server via npx @domainforagents/mcp without pinning a specific version or integrity hash. This creates a software supply-chain risk: a later malicious or compromised package release could be fetched and executed automatically in a privileged local agent/tooling context.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
### Option 2: REST API
Base URL: `https://api.domainforagents.io/api/v1`
All requests need `Authorization: Bearer YOUR_API_KEY` (except account creation).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
### Option 2: REST API
Base URL: `https://api.domainforagents.io/api/v1`
All requests need `Authorization: Bearer YOUR_API_KEY` (except account creation).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
### Option 2: REST API
Base URL: `https://api.domainforagents.io/api/v1`
All requests need `Authorization: Bearer YOUR_API_KEY` (except account creation).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
### Option 2: REST API
Base URL: `https://api.domainforagents.io/api/v1`
All requests need `Authorization: Bearer YOUR_API_KEY` (except account creation).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
### Option 2: REST API
Base URL: `https://api.domainforagents.io/api/v1`
All requests need `Authorization: Bearer YOUR_API_KEY` (except account creation).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
### Option 2: REST API
Base URL: `https://api.domainforagents.io/api/v1`
All requests need `Authorization: Bearer YOUR_API_KEY` (except account creation).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
### Option 2: REST API
Base URL: `https://api.domainforagents.io/api/v1`
All requests need `Authorization: Bearer YOUR_API_KEY` (except account creation).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
### Option 2: REST API
Base URL: `https://api.domainforagents.io/api/v1`
All requests need `Authorization: Bearer YOUR_API_KEY` (except account creation).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
### Option 2: REST API
Base URL: `https://api.domainforagents.io/api/v1`
All requests need `Authorization: Bearer YOUR_API_KEY` (except account creation).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
No signup form needed. One API call:
curl -X POST https://api.domainforagents.io/api/v1/auth/register \
-H "Content-Type: application/json" \
-d '{"name": "my-agent"}'
The skill enables live domain registration and DNS modification, which are real-world, state-changing operations with financial and infrastructure consequences, but it provides no explicit warning or confirmation guidance. In an agent setting, this increases the chance of unintended purchases, domain hijack-like misconfiguration, outages, or directing traffic/email to attacker-controlled infrastructure if invoked from ambiguous prompts.
The skill describes obtaining and using API keys but does not warn that these credentials are sensitive or that responses may contain secrets (api_key, claim_code). In agent workflows, this can lead to accidental logging, prompt leakage, sharing in transcripts, or reuse in insecure environments, enabling unauthorized account actions.