AIKIDO-2026-139254

TL;DR

The SM2 signature verification function in sm-crypto hashes the message together with the caller-supplied public key before it validates that key. doVerifySignature calls getHash, which passes the public key to decodePointHex and dereferences the returned point without a null check, so the guard that would reject a malformed key runs too late. When verification is called with an unparseable public key the decode returns null and the code throws a TypeError instead of returning false, so callers that expect a boolean can crash. The fix moves the public key validity check ahead of the hashing step so a malformed key returns false.