That’s probably not gonna help. The fakes that we have seen in the past have been speaking the Trezor protocol, the problem is that they use one of ~10 pre-defined seed phrases known to the attacker.
What is your firmware version?
Fetch the corresponding firmware image from data/firmware/t2t1 at master · trezor/data · GitHub
Run this script on it, with a challenge that you pick: trezor-firmware/tools/firmware_hash.py at main · trezor/trezor-firmware · GitHub
Lastly, install trezorctl and execute trezorctl fw get-hash <your challenge here>. If your Trezor is subverted, the results will not match.
…of course, it’s also possible that the Trezor rejected the first-time firmware installation, let you set up a wallet with the predefined seed, and then allowed you to overwrite the firmware with the official one. That way you’re still using a compromised seed but you can’t detect tampering unless you physically inspect the device.