morpho-market-creation

• Outcome: Review
• Latest audit: Aug 3, 2026 · 1:55 PM UTC
• Version: 0.6.0

Overview

The skill is a real Morpho/API3 market-deployment helper, but it needs Review because it asks users to store a wallet mnemonic locally and can submit irreversible blockchain transactions with limited safeguards.

Install only if you are comfortable with a local script using a wallet mnemonic to sign real blockchain transactions. Prefer Safe or Etherscan options, use a dedicated low-value deployer wallet instead of a primary wallet, verify chain ID and all contract addresses independently, and treat market/oracle creation as irreversible.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands

Findings (10)

Lp3

Medium

• Category: MCP Least Privilege
• Confidence: 86% confidence
• Finding: The skill declares access to environment-backed execution requirements (`WALLET_MNEMONIC`) but does not declare corresponding permissions, reducing transparency about sensitive capability use. In a skill that performs on-chain deployments and transaction execution, hidden or undeclared env usage can mislead operators about secret handling and increase the chance of unsafe approval or execution.

Tp4

High

• Category: MCP Tool Poisoning
• Confidence: 93% confidence
• Finding: The skill description says it deploys Morpho markets backed by Api3 oracles, but the workflow also deploys Morpho `ChainlinkOracleV2`-style oracle infrastructure, reads arbitrary proxy addresses, and directs users to external deployment paths. This mismatch is dangerous because users may authorize transactions or provide inputs under an incomplete understanding of what contracts are being created and which systems are involved.

Intent-Code Divergence

Medium

• Confidence: 95% confidence
• Finding: The skill states it must never ask for secrets or read `.env` files, yet later depends on `WALLET_MNEMONIC` being set and confirmed in `.env`. Contradictory security instructions weaken user trust boundaries and can normalize unsafe secret handling practices, especially in a deployment skill tied to a live wallet.

Intent-Code Divergence

Medium

• Confidence: 97% confidence
• Finding: These steps explicitly instruct the user to set `WALLET_MNEMONIC` in a `.env` file to enable oracle deployment and market creation, directly conflicting with earlier instructions not to ask for secrets. In the context of blockchain deployment, a mnemonic controls funds and signing authority, so encouraging `.env`-based secret setup materially increases the risk of wallet compromise, accidental leakage, or misuse by tooling.

Description-Behavior Mismatch

High

• Confidence: 96% confidence
• Finding: The script clearly deploys a Chainlink-based oracle via `createMorphoChainlinkOracleV2`, while the skill metadata claims it deploys Morpho markets backed by Api3 oracles. This mismatch is dangerous because operators may rely on the manifest description when making trust and risk decisions, but the actual code wires markets to a different oracle stack with different assumptions, dependencies, and failure modes.

Missing User Warnings

Medium

• Confidence: 87% confidence
• Finding: The README instructs users to run deployment and market-creation scripts that can trigger real blockchain transactions using a wallet mnemonic, but it does not warn about irreversible on-chain actions, gas costs, or the risk of deploying to the wrong network or with incorrect parameters. In a skill specifically designed for contract deployment and market creation, omission of these warnings increases the chance of accidental fund loss or unintended market/oracle deployment by legitimate users.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The script submits a live state-changing transaction to the Morpho contract immediately after loading parameters from disk, with no interactive confirmation, dry-run, or explicit warning to the operator. In a market-creation context, mistakes in chain selection or market parameters are effectively irreversible and can create an unintended market or incur real on-chain costs.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

"type": "module",
  "dependencies": {
    "@api3/dapi-management": "4.32.0",
    "@morpho-org/blue-sdk": "latest",
    "dotenv": "^17.4.2",
    "ethers": "^6.16.0"
  }

• Confidence: 98% confidence
• Finding: Using the version specifier "latest" makes builds non-reproducible and allows any newly published upstream release to be pulled in automatically. In a blockchain market-deployment skill, that creates meaningful supply-chain risk because a compromised or breaking SDK release could alter deployment behavior, introduce malicious code, or cause incorrect on-chain interactions.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

"dependencies": {
    "@api3/dapi-management": "4.32.0",
    "@morpho-org/blue-sdk": "latest",
    "dotenv": "^17.4.2",
    "ethers": "^6.16.0"
  }
}

• Confidence: 90% confidence
• Finding: The caret range on dotenv permits automatic installation of newer patch/minor releases within the major version, which reduces build reproducibility and modestly increases supply-chain exposure. While dotenv is less security-sensitive than blockchain transaction logic, any transitive compromise in the runtime environment could still affect secrets handling or execution behavior.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

"@api3/dapi-management": "4.32.0",
    "@morpho-org/blue-sdk": "latest",
    "dotenv": "^17.4.2",
    "ethers": "^6.16.0"
  }
}

• Confidence: 94% confidence
• Finding: The caret range on ethers allows unreviewed compatible-version updates, which can change cryptographic, signing, provider, or transaction-building behavior without explicit approval. In a skill that deploys Morpho markets and interacts with on-chain contracts, unintended library changes could lead to failed deployments, malformed transactions, or exposure to an upstream compromise.

VirusTotal

VirusTotal findings are pending for this skill version.

Static analysis

No suspicious patterns detected.