::
> Can this create a problem
If you read EVERY stich of Ledger documentation and follow ALL of their best practices, then you’ll be OK. But nobody does that type of diligence. Below is an attack vector for a user that does the bare minimum:
Virus replaces your LL binary with a copy they wrote. Then when you open LL the false binary can prompt for seed entry, or can manipulate your TXN that you are prompted to verify to insert a malicious address or contract. IF you know how to decode TXNs (especially dApps) and read the relevant dependencies then you can catch this before signing. But like I said, nobody does that type of diligence.