T01 · Skill Instruction Hijacking
- Location
SKILL.md:124- Finding
Mandatory Use of Mutable Remote Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherently about Solana wallet payments, but it tells agents to follow changeable remote instructions in a payment flow.
Review this skill before installing in production payment projects. Prefer a version that uses the bundled reference files or commit-pinned links, pin npm dependencies with a lockfile, disclose wallet auto-reconnect behavior, and verify that every transaction shown to the user matches the intended amount, currency, and recipient before signing.
SKILL.md:124Mandatory Use of Mutable Remote Instructions
references/WALLET_INTEGRATION.md:6Wallet Dependencies Are Installed Without Version or Integrity Pinning
SKILL.md:71Core Solana Dependency Resolution Is Not Fully Reproducible
Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
### Parameters (`BuildAcceptPaymentParams`)
| Parameter | Type | Description |
| ------------------ | ---------------------------- | ---------------------------------------------------------------------------------------------------- |
| `user` | `PublicKey` | The payer's wallet address |
| `currencyMint` | `PublicKey` | Mint address of the payment currency (USDC, wSOL) |
The markdown instructs users to enable autoConnect on the wallet provider, which can automatically reconnect to a previously selected wallet when the app loads. The document does not warn that this affects wallet connection behavior or user privacy expectations, even though it changes how the application interacts with the user's wallet.
The layout example sets <html lang="en">, which enforces an English locale in the sample without mentioning user selection or a region-specific requirement. Under the policy, language constraints should either be optional for the user or clearly justified.