Back to skill

Security audit

solana-payments-wallet-dev

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Solana payments skill, but it needs Review because its examples affect real funds and signing credentials while several safety boundaries are under-specified.

Review before installing or using in production. Pin the skill source and npm dependencies, treat all transfer/wrap/unwrap snippets as real-fund operations, validate recipient, mint, amount, decimals, cluster, and serialized transaction contents before signing, and keep Privy app secrets and treasury authorization keys in server-side secret storage only. For nullifiers, use a deterministic or persisted operation identifier for retries rather than generating a fresh random ID each time.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (2)

T09 · Insecure Skill Coding Practices

Warning
Location
references/nullifiers.md:39
Finding

Random nullifier identifiers fail to enforce idempotency across repeated business operations

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Note
Location
SKILL.md:72
Finding

Security-sensitive dependencies are installed through mutable tags and unpinned versions

Content
View full analysis
Remediation
View remediation
\ @lightprotocol/stateless.js= \ @solana/web3.js= \ @solana/spl-token= ``` 2. Commit `package-lock.json` or another supported lockfile and use `npm ci` in CI and production builds. 3. Review and approve dependency updates through a controlled pull-request process rather than resolving new releases during deployment. 4. Verify registry provenance, package publisher identity, integrity hashes, and release signatures where available. 5. Audit direct and transitive dependencies with suitable software-composition-analysis tooling. 6. Consider disabling lifecycle scripts during installation where compatible: ```bash npm ci --ignore-scripts ``` 7. Run installation and build jobs in isolated, least-privileged environments without production signing credentials. 8. Keep Privy secrets and treasury authorization material out of development and dependency-installation environments. 9. Validate transaction program IDs, account addresses, mint, recipient, amount, and serialized message content immediately before signing. 10. Prefer stable, audited releases over beta tags for production payment and wallet systems. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)

Rp1

Medium
Category
MCP Rug Pull
Confidence
89% confidence
Finding

The skill instructs users to install from an unpinned remote source using npx skills add Lightprotocol/skills, which can fetch whatever content is current at execution time. If the upstream repository, package resolution, or dependency chain is compromised, users may ingest altered skill content or tooling without version integrity guarantees.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This documentation provides ready-to-use examples for transfer, wrap, and unwrap flows that directly move tokenized assets, but it does not include explicit safety guidance about validating recipient addresses, token mint, amount, network, or the irreversibility of submitted transactions. In a payments-and-wallets skill, that omission increases the chance that integrators ship unsafe UX or automation that can cause permanent user fund loss through operator error or mis-signing rather than a protocol exploit.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The Node.js example sends a wallet authorization private key to Privy as part of the signing request, which is highly sensitive signing material. Even if this is required by the provider's API, documenting and encouraging this pattern without explicit warnings, scope restrictions, or secret-handling guidance can lead developers to expose treasury signing authority in backend logs, misconfigured environments, or third-party services.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This markdown file includes examples for sending tokens, wrapping from SPL, and unwrapping to SPL, which are user-asset affecting blockchain operations. The document explains how to perform them but does not include any warning about spending funds, network fees, or the irreversibility of submitted transactions.

Content

No source excerpt is available for this finding.