Skip to content
Chain Defenders

Research · Web3 Security · High

Missing PDA binding allows claims against the wrong vault

Claim instructions accepted registry accounts from another configuration, allowing an attacker to use one configuration’s pending claims against another vault.

9 November 2026

What went wrong

ClaimPendingPayouts and ClaimPendingBonuses checked the registry's recipient or referrer field, but did not bind the registry address to the configuration supplied for the claim.

// ClaimPendingPayouts - VULNERABLE
#[account(
    mut,
    constraint = payout_registry.recipient == recipient.key()
)]
pub payout_registry: Account<'info, PayoutRegistry>,

// ClaimPendingBonuses - VULNERABLE  
#[account(
    mut,
    constraint = referrer_registry.referrer == referrer.key()
)]
pub referrer_registry: Account<'info, ReferrerRegistry>,

A registry could belong to the program and deserialize correctly while still belonging to a different configuration. Matching the recipient or referrer did not establish that relationship.

Why it mattered

The report describes an attacker accumulating a pending claim in a configuration backed by a worthless token, then supplying that registry to a claim against a USDC-backed configuration. The program could read the pending amount from the first registry while paying from the second configuration's vault.

The missing check therefore crossed an accounting boundary: a claim recorded for one configuration could authorize a transfer from another. Validating the account's type and recipient alone did not protect the vault.

The fix

The recommended mitigation is to add Anchor seeds and bump constraints. The expected registry address must include the active configuration's key and the recipient or referrer key, using the appropriate registry seed prefix.

These constraints bind the supplied registry to the same configuration as the vault being used. The public report records the finding as Acknowledged; the recommendation should not be read as confirmation that it was implemented.

Takeaway

Validate relationships between accounts as well as each account individually. A valid account from the wrong configuration can break isolation between vaults.

Finding status: Acknowledged.

Shipping something similar? We review the code before it holds money.

Request an audit