solana-anchor
Skill36 starsChanged 5 months agoMITView on GitHub
Detect bug classes specific to Solana / Anchor (Rust) programs — missing signer checks, missing account owner checks, account-confusion / type-cosplay without discriminator validation, unchecked AccountInfo, non-canonical PDA seeds/bumps & seed collisions, missing has_one/constraint, CPI to unverified programs, close-account lamport-drain & revival, sysvar spoofing, and arbitrary-account substitution. Activate on any `.rs` file with `use anchor_lang`, `#[program]`, `#[derive(Accounts)]`, `#[account]`, `Signer<'info>`, or `AccountInfo`.
In this repository44 other files it gives its agents.
- access-controlSkill
- approval-issuesSkill
- caching-and-incrementalSkill
- centralization-riskSkill
- confidence-scoringSkill
- cosmwasmSkill
- cross-chain-messagingSkill
- cross-contract-stateSkill
- delegatecall-risksSkill
- diamond-eip2535Skill
- dos-vectorsSkill
- erc1271-contract-signaturesSkill
- erc4337-account-abstractionSkill
- erc4626-inflationSkill
- false-positive-feedback-loopSkill
- fee-on-transferSkill
- flash-loan-attacksSkill
- initializationSkill
- inline-assemblySkill
- integer-issuesSkill
- intents-erc7683Skill
- known-good-comparisonSkill
- liquidation-cascadeSkill
- mev-frontrunningSkill
- mev-pbsSkill
- multi-pass-self-critiqueSkill
- oracle-manipulationSkill
- oracle-redundancySkill
- permit2-patternsSkill
- pragma-and-addressesSkill
- progress-and-streamingSkill
- reentrancySkill
- restaking-eigenlayerSkill
- selfdestruct-eip6780Skill
- signature-malleabilitySkill
- signature-replaySkill
- storage-layoutSkill
- stylus-rustSkill
- token-compatibilitySkill
- tx-context-misuseSkill
- unchecked-callsSkill
- ve-lock-governanceSkill
- vyper-specificSkill
- zk-verifier-bugsSkill
The file
Files
Solana / Anchor (Rust) detection
When this applies
- Any
.rsfile importinganchor_lang(use anchor_lang::prelude::*) - Macros
#[program],#[derive(Accounts)],#[account],#[instruction(...)] - Account wrappers
Signer<'info>,Account<'info, T>,AccountInfo<'info>,UncheckedAccount,Program<'info, T>,Sysvar<'info, T> - PDA derivation:
seeds = [...],bump,find_program_address,create_program_address - CPI:
CpiContext,invoke,invoke_signed,*_cpi
Solana has no implicit caller. Every authority, ownership, and identity invariant must be asserted explicitly in the account struct or handler.
Detection patterns
Missing signer check (CRITICAL)
#[derive(Accounts)]
pub struct Withdraw<'info> {
pub authority: AccountInfo<'info>, // ← not Signer; nobody proves they're authority
#[account(mut)]
pub vault: Account<'info, Vault>,
}Signal: an "authority"/"owner"/"admin" account typed AccountInfo/UncheckedAccount instead of Signer<'info>, or a handler reading ctx.accounts.x without checking x.is_signer. Anyone passes the real authority's pubkey without their signature.
Missing owner check / arbitrary account substitution (CRITICAL)
let data = ctx.accounts.state.to_account_info();
let state = State::try_from_slice(&data.data.borrow())?; // ← no owner checkSignal: deserializing from a raw AccountInfo/UncheckedAccount without verifying account.owner == program_id, or using Account<T> for data but not constraining which account. An attacker passes a fake account they own with crafted bytes. Account<'info, T> checks owner+discriminator; raw AccountInfo checks nothing.
Type cosplay / missing discriminator validation (HIGH)
let user: UserAccount = UserAccount::try_from_slice(&info.data.borrow())?; // ← any 8-byteSignal: try_from_slice / try_deserialize_unchecked on raw data, bypassing the Anchor 8-byte discriminator. A different account type with the same layout (e.g. Config passed where User is expected) is accepted. Use Account<'info, T> so Anchor enforces the discriminator.
Non-canonical PDA bump / seed collision (HIGH)
let (pda, _bump) = Pubkey::create_program_address(
&[b"vault", user.key().as_ref(), &[user_supplied_bump]], // ← attacker bump
program_id,
)?;Signal: create_program_address with a caller-supplied bump (multiple valid PDAs → forgeable accounts), bumps not stored/re-checked against the canonical one, or seeds that omit a discriminator so ["vault", x] collides with ["vault", x] of another domain. Use find_program_address (canonical bump) or Anchor seeds+bump and persist bump.
Missing has_one / constraint linking accounts (HIGH)
#[derive(Accounts)]
pub struct Update<'info> {
#[account(mut)] // ← no has_one = authority
pub config: Account<'info, Config>,
pub authority: Signer<'info>, // signs, but is never tied to config.authority
}Signal: a Signer that's never bound to the data account it should control — no #[account(has_one = authority)] or #[account(constraint = config.authority == authority.key())]. Any signer updates any config. Same for mint, owner, vault relationships.
CPI to unverified program (HIGH)
let cpi = CpiContext::new(ctx.accounts.token_program.to_account_info(), ...);
token::transfer(cpi, amount)?; // ← token_program is an unconstrained AccountInfoSignal: CpiContext::new whose program account isn't constrained to the expected Program<'info, Token> / known program id, or invoke/invoke_signed to a caller-supplied program. Attacker passes a malicious program at the token_program slot. Type it Program<'info, Token> or assert the key.
close-account lamport drain / revival (HIGH)
**ctx.accounts.dest.lamports.borrow_mut() += account.lamports();
**account.lamports.borrow_mut() = 0; // ← manual close, no discriminator zeroingSignal: manual lamport zeroing without wiping the discriminator/data, or #[account(close = ...)] whose data the attacker can re-fund in the same tx (revival attack) before it's GC'd. Use Anchor close = recipient (it zeroes the discriminator) and don't reuse closed accounts in the same instruction.
Sysvar / clock spoofing (MEDIUM-HIGH)
pub clock: AccountInfo<'info>, // ← passed as raw account, not Sysvar
let now = Clock::from_account_info(&ctx.accounts.clock)?.unix_timestamp;Signal: Clock/Rent/Instructions sysvars typed as AccountInfo/UncheckedAccount rather than Sysvar<'info, Clock> or fetched via Clock::get(). An attacker substitutes a fake sysvar account with controlled time/data.
Unchecked AccountInfo used for value flow (MEDIUM)
/// CHECK: comment present but the account is then trusted for transfers
pub recipient: UncheckedAccount<'info>,Signal: UncheckedAccount/AccountInfo (or a /// CHECK: with no real validation) that's subsequently used as a transfer destination, authority, or data source. The CHECK comment silences Anchor but doesn't add a constraint.
Severity rubric
| Pattern | Severity | Notes |
Authority as AccountInfo, no signer proof | Critical | Impersonate any authority |
| Deserialize raw account, no owner check | Critical | Fake-account substitution |
| Type cosplay (no discriminator) | High | Wrong account type accepted |
| Caller-supplied / non-canonical PDA bump or seed collision | High | Forge PDA-owned accounts |
Missing has_one/constraint linking signer↔data | High | Any signer mutates any record |
| CPI to unconstrained program account | High | Malicious program at slot |
| Manual close / revivable closed account | High | Lamport drain / reuse |
Sysvar passed as AccountInfo | Medium | Spoofed clock/rent |
UncheckedAccount used for value flow | Medium | Depends on later checks |
Remediation patterns
- Type authorities as
Signer<'info>and assert their relationship with#[account(has_one = authority)]orconstraint =. - Use
Account<'info, T>(not rawAccountInfo) so Anchor enforcesowner == program_idAND the 8-byte discriminator; nevertry_from_slice/try_deserialize_uncheckedon untrusted accounts. - Derive PDAs canonically — Anchor
seeds = [...]+bump(orfind_program_address), store the bump, include a domain discriminant in seeds to prevent collisions. - Constrain CPI program accounts to
Program<'info, Token>/known ids; validate any account passed toinvoke/invoke_signed. - Close with
#[account(close = recipient)]so the discriminator is zeroed; don't reuse a closed account within the instruction. - Fetch sysvars via
Clock::get()orSysvar<'info, Clock>, never a raw account. - Resolve every
/// CHECK:with an actual key/owner constraint, not just a comment.
False-positive notes
- An
AccountInfo/UncheckedAccountwith a real#[account(address = KNOWN_PUBKEY)]or in-handler key assertion is validated — don't flag it as unchecked. Account<'info, T>already enforces owner + discriminator; type-cosplay and owner-check findings apply to RAWAccountInfo/try_from_slicepaths only.- A
Signerthat legitimately needs no data binding (e.g. a fee payer that only pays rent) doesn't needhas_one. init/init_if_neededaccounts set their own owner to the program — owner-check findings don't apply at init.
Related
- [[access-control]] — signer, owner, and has_one constraints are Solana's entire auth model
- [[signature-replay]] — Solana txs need recent-blockhash + nonce discipline; instruction-level replay across PDAs
PDA Validation & Account Constraints
Added program-derived address (PDA) validation for Anchor programs. The skill now detects:
- Missing
seedsconstraint on PDA accounts initialized via CPI - Mismatched bump seeds between
initand subsequentmutconstraints - Unchecked account discriminators in cross-program invocations
- Missing
has_oneconstraints on associated token accounts
Detection Example
// VULNERABLE: Missing seeds constraint on PDA init
#[derive(Accounts)]
pub struct InitializePool {
#[account(init, payer = admin, space = 8 + Pool::SIZE)]
pub pool: Account<'info, Pool>, // ❌ Missing PDA seed derivation
pub admin: Signer<'info>,
}The skill verifies Anchor IDL account constraints against actual on-chain validation and flags mismatches that could allow fake PDA injection attacks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

