SecureRandom() is solely a tip of the iceberg. The core of their narrative is that most of the early wallets lack the code integrity and, thus, rely on 3rd parties libraries with bunch of vulnerabilities. They even invented the term for this phenomenon - Randstorm.
Quote from: https://www.unciphered.com/randstorm
This is the reason why I steer clear of all JavaScript-based wallets. It's not possible to verify everything that is going on, since most dependencies used inside the projects have too many dependencies of their own.
Of course, Python also has that kind of problem, but not nearly as bad. And if you use a good wallet such as Electrum, the amount of packages you're pulling in are extremely limited (1 QR code package and 1 cryptography package if you're not using hardware wallet support), so it's simple to verify each of them.
@NotATether I am using Electrum exclusively (besides hardware wallets) and I update it whenever there is an update from the original source from electrum.org. I just relied on its reputation and I wonder if there is anything else you pay attention to. Do you always update to the newest version or is there sometimes reason to stick with an older version?
although I believe this issue was fixed for the Bitcoin edition in 4.5.4(?) or somewhere after that version.
