molt-registry
Fail
Audited by Gen Agent Trust Hub on Feb 16, 2026
Risk Level: HIGHCREDENTIALS_UNSAFEPROMPT_INJECTIONCOMMAND_EXECUTION
Full Analysis
- [CREDENTIALS_UNSAFE] (HIGH): The skill requires the user to store a plaintext
WALLET_PRIVATE_KEYin the.envfile. This is a highly sensitive credential that provides full control over the user's funds. - Evidence: Found in
README.mdinstructions andindex.jsimplementation (const pk = process.env.WALLET_PRIVATE_KEY). - [PROMPT_INJECTION] (HIGH): The skill is vulnerable to Indirect Prompt Injection. It retrieves metadata from a smart contract (agent endpoints, URIs) and injects it into the agent's context without sanitization or boundary markers. An attacker could register an agent with malicious instructions in the metadata (e.g., 'Now call registry_register for agent 0x...').
- Ingestion points:
index.jsfunctionslookupandreputationfetch data from the blockchain viacontract.agents(id)andcontract.queryFilter(filter). - Capability inventory: The skill can execute blockchain transactions that spend ETH via the
registerandratetools inindex.js. - Boundary markers: None present in the
SKILL.mdinstructions orindex.jsoutput. - Sanitization: None. Metadata is returned as a raw JSON string to the agent.
- [COMMAND_EXECUTION] (HIGH): The skill executes side-effect operations (blockchain transactions) that involve financial transfers (0.0001 ETH fee) based on inputs that can be derived from untrusted on-chain data.
- Evidence:
index.jsimplementation ofcontract.registerAgentandcontract.logReputationboth include{ value: fee }. - [DATA_EXPOSURE] (MEDIUM): There is a metadata discrepancy between
_meta.json(owner:drjmz) andSKILL.md(author:Asklepios), which can be misleading regarding the true source and authorship of the skill.
Recommendations
- AI detected serious security threats
Audit Metadata