Security audit
Security checks for vulnerabilities and agentic risk
The skill is purpose-aligned for Solana on-chain storage, but it gives high-impact wallet, payment, and installer guidance with insufficient guardrails.
Review carefully before installing. Use a dedicated low-value devnet wallet first, protect any Solana keypair JSON as a private key, avoid storing secrets or personal data on-chain, pin and verify dependencies/installers where possible, and manually confirm payment recipient, amount, token, network, and service identity before signing any transaction.
references/setup.md:10Remote Installer Is Downloaded and Executed Without Integrity Verification
references/setup.md:36Security-Sensitive npm Dependencies Are Installed Without Version Pinning
skill.md:130Weak XOR-Based Obfuscation Is Demonstrated for Permanent On-Chain Secrets
references/x402-payments.md:35Payment Transaction Trusts an Unauthenticated Quote Destination and Amount
The documentation instructs users to set ANCHOR_WALLET=/path/to/solana/keypair.json without warning that this file points to highly sensitive signing credentials. In a skill focused on on-chain writes and paid inscription, normalizing direct use of a local keypair path increases the risk of accidental exposure through misconfiguration, insecure file permissions, logs, screenshots, or unsafe automation environments.
This markdown file describes pushInstruction being used to delete existing rows by passing an empty string, but it does not provide a user-facing warning about the potential impact on stored data. Under the markdown criteria for missing user warnings, destructive or data-affecting behavior should be disclosed clearly.
The setup instructions tell users to generate a Solana keypair file on disk and configure it as the active wallet, but they do not warn that this file contains the private key and must be protected like a secret. In the context of a skill that later recommends mainnet use with real SOL, a user may reuse this wallet or mishandle the keypair, leading to fund loss or unauthorized signing if the file is exposed.
The document’s primary workflow explains how to pay for and permanently inscribe files on-chain, but does not prominently warn users before the workflow that uploaded data becomes public, immutable, and effectively undeletable. In this skill context, that omission is materially dangerous because users may upload sensitive, regulated, or proprietary data under the mistaken assumption it can later be removed or kept private.
The skill presents hanLock as a privacy mechanism for writing data on-chain, but it does not clearly warn that the resulting data is still permanently public and that password-based encoding is not equivalent to strong cryptographic encryption. This can mislead users into storing secrets, credentials, or regulated data on an immutable public ledger under a false sense of confidentiality.
The file describes converting arbitrary data into Korean Hangul syllables and frames that output as useful for privacy. Because this imposes a specific language/script on encoded content without mentioning user choice or opt-in, it may violate a language/locale policy that discourages forcing a locale-specific representation.
No suspicious patterns detected.