I received a sample of the SecuX W20 in early February to review. By mid-February, I had found something that changed how I looked at this device. The screen can be made to show balances, account names, and even scary warning text without any user confirmation on the device itself.
That is not a small issue for a hardware wallet. A hardware wallet should help you verify what you are doing, especially when money is involved. If the screen can display arbitrary information from connected software, then it cannot be treated as fully trusted in all cases.
Watch the video for the full demonstration, unboxing, and setup walkthrough. This article is a written version of that review, with extra focus on what you need to know if you are considering this wallet or already own one.
Why this review is different from a normal hardware wallet review
Most hardware wallet reviews cover the box, setup, accounts, sending, receiving, firmware updates, and mobile support. This video does all of that too. But it also covers a serious trust issue: connected software can change what appears on the device screen without asking you to confirm those changes.
I want to be clear about the risk here. A malicious or compromised wallet application could potentially make your SecuX W20 display false balances, fake account names, or alarming messages such as “critical hardware fault” or instructions that scare you into doing something unsafe. That kind of behavior is especially dangerous for newer users who are trained to trust what they see on the device screen.
The core problem is this: a trusted-looking screen can show untrusted information. That makes it possible for software on your computer to manipulate what you believe is happening.
Disclosure timeline and SecuX response
I found the issue in mid-February while testing what the device would allow connected software to do. I then tried to contact SecuX about it. At the time, SecuX did not appear to have a clear responsible disclosure policy that I could find, unlike some other hardware wallet companies that publish their process for reporting security issues.
I followed a similar approach to what is commonly used in responsible disclosure: report the issue privately and give the vendor time to respond and fix it. Since then, SecuX acknowledged there was a problem. However, they also removed open-source tools associated with the platform. That reduced third-party auditability and made it harder for independent people to inspect or build on the same tooling that had previously been available.
I am not publishing the actual code used in the demonstration. I do not want to make the situation worse by handing someone a ready-made exploit. But anyone malicious who understands this kind of issue could reproduce something similar quickly. The lesson is not about one piece of code. It is about how much control connected software has over what the device displays.
Local wallet, Secux-Connect library, and the display problem
To investigate, I downloaded a local copy of the SecuX browser wallet from their website. This allowed me to run the same kind of wallet interface locally and test it against the hardware device.

I also looked into an open-source library called secux-connect, which was available on npm and used by the device API. Inside that library, I found functions related to querying accounts, changing account names, changing balances shown in the interface, deleting accounts, and other operations that could happen automatically behind the scenes.

This matters because it shows how much of the device experience depends on software running on your computer or browser. If that software is malicious, compromised, or even just poorly designed, it can influence what you see and do.
In the demonstration, I connected to the wallet and changed account information without any confirmation prompt appearing on the hardware wallet screen. The changes happened instantly. I could make balances display whatever value I wanted. I could also put arbitrary text into the balance lines.

That is where it gets dangerous. A user might open their browser wallet, see a scary-looking error message in the browser, then look down at their hardware wallet and see something that looks like an official warning. That combination could confuse people into doing unsafe things, such as entering their seed phrase somewhere they should not or following instructions from a fake update page.
This is similar in spirit to older phishing problems where trusted-looking software displayed untrusted messages. The screen becomes a place you trust, but the information on it may not be trustworthy unless the device itself verifies and confirms that information.
What you can safely trust on the SecuX W20 screen
If you have or are considering a SecuX W20-class wallet, this is the most important part of the article: do not treat every piece of text on the screen as reliable.
Based on what I demonstrated and discussed in the video, the safest approach is to trust only these two types of device-side confirmation:
-
Address confirmation when receiving funds.
When you are receiving coins, verify that the address shown on the device matches the address you intend to use. This should be treated as a critical check. -
Transaction details when signing/sending funds.
Before confirming a send, verify the transaction details on the device, including the amount and destination where possible. Do not rely only on what the browser or desktop software says.
Everything else shown on the screen should be taken with caution. That includes balances, account names, portfolio summaries, warning messages, update prompts, and other informational text that may come from connected software.
A hardware wallet is most valuable when it gives you a trustworthy way to confirm critical actions. If the device can display arbitrary unconfirmed information in places users naturally trust, then the design needs safeguards such as user approval for changes, clear separation between trusted and untrusted content, or options to disable certain displays. Without those safeguards, the screen cannot be fully trusted.
Unboxing and initial setup
After covering the security issue, I moved on to the normal review: unboxing, setup, accounts, hidden wallet, firmware update, receiving, sending, and Bluetooth mobile access.
The box contains the device and documentation. The W20 is a basic hardware wallet with a color touchscreen. It supports multiple coins through its companion software, including Bitcoin, Ethereum, Litecoin, and others shown in the interface during testing.

Step 1: Start the device and set a PIN
To begin setup, connect the device and start it. You will be asked to choose a PIN. In my test, I entered a temporary PIN twice.

One confusing part of the setup is what happens if your first PIN entry and confirmation do not match. The device does not simply let you retry the second entry automatically. If the confirmation fails, you need to exit that flow and start again from the beginning. That may sound minor, but for a beginner it can be frustrating at exactly the moment they are trying to learn how the wallet works.
Step 2: Create a new wallet and write down the recovery seed
After setting the PIN, I chose to set up as a new wallet. The device then generated a 24-word BIP39 recovery seed. You need to write this down carefully in a safe place. Do not share it. Do not store it online. Do not type it into a website or app unless you fully understand why and how the legitimate process works.

My practical tip: use pencil rather than pen if possible, because pencil can be easier to preserve if the paper gets wet. More importantly, make your writing legible. This seed is your wallet. If you lose it or write it down badly enough that you cannot read it later, recovery becomes much harder.
The device verified all 24 words during setup. That is good. A full 24-word seed gives more entropy than a 12-word seed, and the touchscreen makes entering and confirming those words manageable.
Step 3: Add cryptocurrency accounts
After creating the wallet, I connected through USB/WebUSB in the browser and added accounts for different coins. The interface let me select coins such as Bitcoin, Ethereum, and Litecoin, then add named accounts.

Adding multiple accounts worked, but the process was not always smooth. In some cases, adding an account kicked the interface back to a disconnected or starting state and required reconnecting. That is not necessarily dangerous, but it is clunky for users who expect a clean guided experience.

Step 4: Set up a BIP39 passphrase hidden wallet
The SecuX W20 also supports a hidden wallet using a BIP39 passphrase. This is useful if you want to keep separate funds under an additional layer of protection. The idea is that the same seed can derive different wallets depending on whether a passphrase is used.
To set it up, I went into the device settings and created a hidden wallet with a separate PIN and passphrase. After setup, reconnecting using that hidden-wallet PIN accessed the hidden wallet context. In my test, the hidden wallet initially had no accounts, so I added another Bitcoin account to confirm it behaved like a normal wallet in that context.

A BIP39 passphrase can be very useful, but only if you understand the consequences. If you forget the passphrase, the funds derived from that passphrase may be inaccessible even if you still have the 24-word seed. Keep your backup information organized and test recovery in a safe way before relying on it for large amounts.
If you ever find yourself locked out of a wallet or unsure how to proceed safely with recovery, I also cover recovery-related support options here: recovery services and consultations.
Step 5: Run a firmware update
The device has a firmware update section. In the test, I started an update from the companion interface. The device went through its update process, including bootloader completion, then asked me to reconnect.

Firmware updates are normal for hardware wallets, but they should be handled carefully. You want to make sure you are using the legitimate update process from a trusted source and that the device is not being manipulated by malicious software while connected.
Receiving funds
Receiving is one of the most important workflows to test because it is where address verification matters most. In my test, I sent Litecoin to the wallet. The transaction appeared in the companion interface after confirmation details were available.

The device displayed a receiving address with a QR code and account label. This is one of the places where you should carefully check what you are seeing on the hardware wallet itself, not just in the browser.

One limitation I noticed: the device would show only the first address at that point, while the software side could increment receiving addresses. That is not necessarily a security flaw by itself, but it means you need to be careful about which address you are actually using and verifying.
Sending funds
Sending is where transaction confirmation matters most. I tested sending Litecoin from the wallet. The companion interface showed the send process with account details, balance, recipient field, and amount field.

During testing, I ran into address format issues when trying to use a native Segwit Bitcoin-style address in the test flow. The interface rejected it because only certain legacy or P2SH-style formats were accepted for that particular send path. That is a usability limitation worth knowing about if you rely on modern address formats.

When I sent the test transaction, it appeared in the mempool and then confirmed. The balance refresh in the companion interface was not always immediate, which can be confusing if you are watching closely. That is common with some wallet interfaces, but it reinforces the importance of checking blockchain explorers when needed.

Mobile Bluetooth access
The W20 also supports Bluetooth mobile access. I tested pairing and connection from a browser-based interface. The device showed a Bluetooth status, and once connected, the companion interface could display account information.

The mobile Bluetooth experience worked, but it was not flawless in my testing. At times the interface appeared stuck on a processing or loading state even though the device showed that Bluetooth was connected. That kind of behavior is frustrating and can make users doubt whether the wallet is working correctly.

For a basic user, Bluetooth access is convenient because it allows use with a phone or tablet without a cable. But convenience should not come at the cost of reliability or security clarity. If the software side is unstable, users may misinterpret what is happening on the device.
Is the SecuX W20 worth buying?
This is one of those devices where I was unsure who it is really for even before discovering the display trust issue. It is a fairly basic hardware wallet in terms of features and advanced functionality. Some workflows are clunky, some address formats are limited, and the experience can feel unstable at times.
Then there is the bigger problem: the screen can display information from connected software without sufficient user confirmation. That makes it risky for people who do not deeply understand how hardware wallets work, especially newer users who may trust any warning message they see on a small device screen.
The good news is that this kind of issue should be fixable in software or firmware. The vendor could require approval for certain changes, clearly separate trusted confirmations from untrusted informational displays, improve update verification, and provide better guidance to users about what can and cannot be trusted. Instead, SecuX removed open-source tools and moved toward a more closed approach after the issue was reported. That is not a reassuring response if you are trying to evaluate long-term safety and auditability.
What I would do if I were using this wallet
If I were already using a SecuX W20-class wallet, I would treat it with extra caution:
-
Only trust address confirmation on receive.
Always verify the receiving address on the device before sending funds to it. -
Only trust transaction details when signing.
Check the amount and destination carefully on the hardware wallet itself. -
Do not panic at scary messages.
If you see a warning, error, update prompt, or balance change that looks wrong, stop. Do not enter your seed phrase into a website, app, or browser extension just because a screen tells you to. -
Keep your backup offline and legible.
Your 24-word seed is the most important part of the wallet. Store it safely on paper or another durable medium that you control. -
Know the legitimate recovery process.
For many modern hardware wallets, recovery should happen directly on the device itself. You should never be asked to type your seed into a random website or app as a normal step. If someone asks for your seed phrase, treat it as a red flag unless you fully understand why. -
Check blockchain explorers when in doubt.
If the wallet interface is not refreshing balances or transaction status clearly, verify transactions using an independent explorer.
Final conclusion
The SecuX W20 has some useful features: 24-word seed backup, multiple coin accounts, hidden wallets via BIP39 passphrase, firmware updates, and Bluetooth mobile access. But the most important takeaway from this review is not about coins supported or button layout. It is about trust.
A hardware wallet screen should help protect you, not become another place where malicious software can confuse you. If connected software can change balances, account names, or display warning-style text without user confirmation, then users need to understand exactly what parts of the screen are reliable and what parts may be false.
For me, that changes how I view this device. It is not automatically unsafe in every situation, but it requires a much higher level of caution than I would want from a hardware wallet, especially for beginners. If you are choosing between wallets at a similar price point, also consider whether the company has a responsible disclosure policy and whether its software remains inspectable by third parties. Security is not only about preventing malicious vendors or hackers. It is also about how well the product handles mistakes, poor design decisions, and the inevitable security issues that appear when real people use it in the wild.
Questions from viewers
Common questions from the comments on this video, with my answers.
Which hardware wallet should I buy if I am a beginner or want the safest option?
For most people, especially beginners, the Ledger Nano X is a much better choice. It has safer documentation and onboarding. If you prefer not to use Ledger, a Trezor is also a solid alternative, though be careful with their default passphrase settings if using it with MetaMask. You can check my detailed comparisons for more options.
Is the SecuX W20 safe to use compared to keeping funds on an exchange?
It is still hardware-backed self-custody, so it is better than custodial solutions like exchanges or software wallets. However, you must be aware of the limitations regarding how account names and balances are displayed, as these can be manipulated without confirmation. Generally, I recommend avoiding SecuX devices due to these security risks.
What happens if my hardware wallet breaks, stops working, or becomes obsolete in the future?
The physical device is just a consumable tool. As long as you have your recovery seed phrase backed up offline (non-digital) and stored safely, you can recover your funds on any other compatible device. The device itself breaking does not mean you lose your crypto.
Why was there a PIN entry issue mentioned in the video, and did they fix it?
If you make a typo on the first PIN entry, the workflow gets stuck. This wasn't really 'patched' by updating code; they just removed the vulnerable library from NPM, but it remains available through their official wallet. This is a serious issue because it allows for remote exploitation where attackers can register similar domains to trick users.
My SecuX W20 crashed after a firmware update and shows an error. How do I fix it?
You may have bricked the device. In this case, you will need to contact SecuX Support directly for assistance. If you’d like hands-on help, see wallet recovery services.
Choosing a hardware wallet?
See how this device stacks up against the others I’ve tested: security model, supported coins, backup options and price.
Some links on this site are affiliate links: if you buy through them I may earn a commission at no extra cost to you. It doesn’t change what I recommend.
Found this useful?
These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.







