Back to skill

Security audit

Domain Name Registration For Agents

Security checks for vulnerabilities and agentic risk

Overview

The skill does what it claims, but it enables wallet-funded domain purchases and DNS changes without enough confirmation and safety guidance.

Review carefully before installing. Use a dedicated low-balance wallet, protect any wallet JSON files, pin and verify the Python package where possible, and require a clear quote plus explicit user approval before any domain purchase, DNS deletion/update, or nameserver change.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:14
Finding
Unpinned Third-Party Dependency Used for Financial and Wallet Operations## Vulnerability Details **File Location**: `SKILL.md`, lines 14–18 **Vulnerability Type**: `T08: Insecure Dependencies` **Risk Level**: Medium **Complete Code Snippet**: ```bash pip install agentns-client # For Solana wallet support: pip install agentns-client[solana] ``` ### Technical Analysis The installation instructions retrieve and execute the latest available version of `agentns-client` from PyPI without an exact version constraint, cryptographic hash verification, or a project lockfile. The repository contains no bundled implementation with which to audit the installed package. The dependency is subsequently entrusted with sensitive operations, including creating or loading cryptocurrency wallets, signing authentication messages, processing registrant contact information, making automatic USDC payments, and modifying DNS records. Because the installed artifact can change independently of this reviewed skill, a compromised package release or distribution account could introduce arbitrary code into these high-value workflows. No evidence establishes that the currently published dependency is malicious. The confirmed issue is the absence of reproducible, integrity-verified dependency installation. ### Attack Path 1. An attacker compromises the package publisher account, package repository, release process, or another relevant supply-chain component. 2. The attacker publishes a modified release under the expected `agentns-client` package name. 3. A user follows the documented unpinned installation command and receives the attacker-controlled release. 4. The user imports and invokes the package for wallet creation, authentication, registration, payment, or DNS administration. 5. Malicious package code executes in the user's Python environment and may access information or capabilities exposed during those operations. 6. The package could exfiltrate wallet material or registrant data, redirect transactions, init ...[truncated 827 chars]
Remediation
## Remediation Suggestions 1. Pin `agentns-client` and its optional Solana extra to an exact, security-reviewed version. 2. Publish a lockfile or constraints file covering all transitive dependencies. 3. Provide SHA-256 hashes and require installation with hash verification, such as `pip install --require-hashes`. 4. Verify that the reviewed source repository and the distributed PyPI artifact are reproducibly linked. 5. Automate dependency vulnerability, provenance, and package-integrity checks in the release process. 6. Run the client in an isolated virtual environment or container with minimal filesystem and network permissions. 7. Use a dedicated, low-balance wallet rather than a wallet holding unrelated assets. 8. Require explicit user confirmation of the amount, destination, network, and domain before each payment. 9. Protect wallet files with restrictive filesystem permissions and avoid storing them in shared project directories. 10. Document package provenance and a controlled upgrade procedure requiring review before changing the pinned version.
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The documentation states that domain registration is handled automatically after wallet login and setup, but it does not clearly warn that this action will spend USDC from the connected wallet. Because the skill is user-invocable and centered on wallet-based payments, insufficient payment transparency can lead to unintended financial loss from agent-initiated purchases.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The skill documents DNS record and nameserver changes as routine operations without warning that incorrect values can immediately disrupt website, email, and other domain-dependent services. In an agent-invocable skill, this omission increases the chance an autonomous or inattentive user triggers destructive configuration changes on a live domain.

Static analysis

No suspicious patterns detected.