AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 60 Bitcoin

feat(solana): show base account for create account with seed

Public commit record

What the developer wrote

Authored by Jakub Janků

95/100 · Strong
feat(solana): show base account for create account with seed

The base account is the field that allows the user to easily confirm
that the newly created account will belong to them. If the base account
differs from the signing account, the user may be transferring lamports
to a new attacker-controlled account. While it is true that the address
of the new account is shown already (and therefore the user doesn't
transfer assets to an unknown destination), the user cannot easily verify
ownership of this new account without the base address --- the new
address is a hash of the base address, the seed, and the owner.

(cherry picked from commit 8bda3f3a6e4b44aef47469549cdf3d62def56c2e)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This update improves the Trezor hardware wallet's Solana transaction confirmation screen. When a user creates a new Solana account from a seed, the device now also displays the 'base account' used to derive that new address. Without this, a malicious app could ask the device to create an account controlled by someone else while still making the destination look derived from the user's own keys. The change helps users spot when the new account won't actually belong to them before they approve the transaction.

Recommended action

Users should update to firmware containing this commit. Developers should ensure the new 'Base account' field is rendered clearly during on-device confirmation, especially when it differs from the signer. No immediate incident response is indicated.

Security signals we found

01

UI confirmation of attacker-controlled base account for derived Solana addresses

02

Prevents social-engineering/phishing where created account appears user-derived but is not

03

Changelog explicitly labels change as security-relevant

04

No signing or parsing logic changed; risk is reduced user-misapproval

Risk score

Why this scored 60/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 10/15
Affected reach 8/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.