Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly documents legitimate Moralis blockchain lookups, but it includes a metadata-resync operation that can change external state despite being presented mainly as a data-query skill.
Install only if you intend to use Moralis as a third-party blockchain data provider. Protect MORALIS_API_KEY, avoid exposing it in logs or shell history, and treat wallet addresses, portfolio/history, profitability, and net-worth lookups as sensitive financial intelligence. Require explicit user confirmation before using reSyncMetadata because it updates/resyncs external NFT metadata state rather than merely reading data.
This skill is described as a query-oriented blockchain data API, but the documented endpoint performs a state-changing resync/update operation on NFT metadata. In an agent context, exposing a mutating operation under a data-retrieval skill can cause unintended external side effects, surprise writes, or abuse of privileged API keys when the user only expected read-only behavior.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
### API Key (optional)
**Never ask the user to paste their API key into the chat.** Instead:
1. Check if `MORALIS_API_KEY` is set in the environment (try running `[ -n "$MORALIS_API_KEY" ] && echo "API key is set" || echo "API key is NOT set"`).
2. If not set, offer to create the `.env` file with an empty placeholder: `MORALIS_API_KEY=`
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## Data Type Assumptions (MOST COMMON BUG SOURCE)
**NEVER assume these without checking the rule file:**
| Field | Wrong Assumption | Reality |
| -------------- | --------------------------- | --------------------------------------- |
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST "https://deep-index.moralis.io/api/v2.2/discovery/tokens" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST "https://deep-index.moralis.io/api/v2.2/discovery/tokens" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
This skill explicitly directs transmission of user-supplied NFT identifiers to an external service using an authenticated API call. In this skill's context, external transmission is expected functionality, but it is still security-relevant because wallet, NFT, and transaction-related queries can reveal sensitive financial associations, and the example does not document consent, minimization, or handling of the API key.
curl -X POST "https://deep-index.moralis.io/api/v2.2/nft/getMultipleNFTs?chain=eth" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST "https://deep-index.moralis.io/api/v2.2/tokens/analytics" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST "https://solana-gateway.moralis.io/token/mainnet/metadata" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST "https://deep-index.moralis.io/api/v2.2/erc20/prices?chain=eth&include=" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST "https://solana-gateway.moralis.io/token/mainnet/prices" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST "https://deep-index.moralis.io/api/v2.2/nft/metadata?chain=eth" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST "https://deep-index.moralis.io/api/v2.2/nft/0x524cab2ec69124574082676e6f654a18df49a048/nfts-by-traits?chain=eth&format=decimal" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
The documentation instructs users to make an authenticated request to Moralis using both a wallet address and an API key, but it does not warn that this data is sent to a third-party service. While wallet addresses are public on-chain identifiers, associating a queried address with a specific user, workflow, or internal investigation can still create privacy, attribution, and data-governance risks, and exposing API-key usage patterns may also have operational sensitivity.
This skill documents an API call that retrieves a wallet’s full Solana portfolio, including balances, tokens, and NFTs, but provides no user-facing warning that the queried address and resulting financial profile may be sensitive. In an agent context, users may supply their own wallet or ask about third-party wallets without understanding the privacy implications, which can enable unwanted financial profiling or disclosure of holdings.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST "https://deep-index.moralis.io/api/v2.2/tokens/analytics/timeseries?timeframe=1d" \
-H "accept: application/json" \
-H "X-API-Key: $MORALIS_API_KEY" \
-H "Content-Type: application/json" \
This skill instructs callers to send a wallet address and API key to a third-party service but provides no privacy or data-handling warning. Wallet history can reveal holdings, counterparties, behavior, and other sensitive financial metadata, so users may unknowingly disclose transaction intelligence to an external provider.
This documentation instructs agents to send wallet addresses and derived financial portfolio data to Moralis, a third-party API, but does not disclose the privacy implications or advise user consent. Wallet addresses are pseudonymous rather than anonymous, and net-worth lookups can expose sensitive holdings and behavioral data when correlated across chains.
The skill instructs the agent to send a user-supplied wallet address to Moralis, a third-party API, without any disclosure that wallet-related data will be transmitted off-platform. While blockchain addresses are often public, they can still be sensitive in context because they may reveal financial holdings, trading behavior, and identity-linked activity when correlated with other information.
Labeling the operation as GET while the documentation says it updates or resyncs metadata is dangerous because GET is widely assumed to be safe and side-effect-free. Agents, middleware, caches, link previewers, or automated tooling may invoke such an endpoint more freely, increasing the chance of accidental state changes or repeated triggering.
The documentation presents metadata resync as a simple operation without warning that it changes external state or may trigger downstream fetches and updates from token URIs. In an agent setting, this omission makes the skill more dangerous because users and orchestrators may treat it like passive data access, leading to unintentional writes or externally triggered processing.
The markdown states the skill should be used for wallet balances, transaction history, profitability, net worth, and other address-linked data, which implies sending user-supplied wallet identifiers and queries to the Moralis API. While authentication setup is documented, there is no explicit warning that requested wallet/address data will be transmitted to a third-party service.
This markdown file includes a curl example that requires the X-API-Key header via $MORALIS_API_KEY, which involves use of a credential. The description does not include any warning or note about handling secrets, even though SQP-2 for markdown files covers omissions related to privacy or system integrity.
The document instructs users to call an authenticated third-party API using wallet address and protocol parameters, but it does not clearly disclose that this data is sent to Moralis. Wallet addresses and DeFi position lookups can reveal sensitive financial holdings and behavior, so lack of disclosure can create privacy, compliance, and user-consent issues even if no direct code execution risk exists.
This markdown file includes a curl example that sends an API key from the MORALIS_API_KEY environment variable, but the documentation does not warn users that a credential is required or that it will be transmitted in the request header. For markdown files, credentials and network-affecting behavior should be disclosed when relevant to user privacy or system integrity.
This markdown file includes a curl example that sends an API key from the MORALIS_API_KEY environment variable in an HTTP header, but the document does not warn users that they must provide and protect a credential when invoking the request. For markdown files, credential use and network transmission should be disclosed when they may affect privacy or security posture.
No suspicious patterns detected.