fix: lattice sign typed signature verification error

[Akaryatrh]

Description

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@chainsafe/as-sha256@0.3.1	None	0	165 kB	dapplion
npm/@chainsafe/persistent-merkle-tree@0.4.2	None	0	112 kB	dapplion
npm/@chainsafe/ssz@0.9.4	None	0	468 kB	dapplion
npm/@scure/base@1.1.7	None	0	122 kB	paulmillr
npm/bitwise@2.1.0	None	0	120 kB	florianwendelborn
npm/case@1.6.3	None	0	39.1 kB	nbubna
npm/crc-32@1.2.0	None	0	13.3 kB	sheetjs
npm/elliptic@6.5.4	None	+1	160 kB	indutny
npm/eth-chainlist@0.0.498	None	0	1.13 MB	zanechua
npm/eth-eip712-util-browser@0.0.3	None	+1	125 kB	asmiller1989
npm/exit-on-epipe@1.0.1	None	0	5 kB	sheetjs
npm/gridplus-sdk@2.5.1	environment, network	+2	789 kB	asmiller1989
npm/printj@1.1.2	None	0	113 kB	sheetjs

🚮 Removed packages: npm/@scure/base@1.1.9, npm/@sovpro/delimited-stream@1.1.0, npm/bitwise@2.2.1, npm/borc@3.0.0, npm/crc-32@1.2.2, npm/elliptic@6.5.7, npm/eth-chainlist@0.0.519, npm/gridplus-sdk@2.7.1, npm/iso-url@1.2.1, npm/json-text-sequence@0.3.0

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/elliptic@6.5.4, npm/@noble/secp256k1@1.6.3, npm/exit-on-epipe@1.0.1, npm/crc-32@1.2.0, npm/printj@1.1.2, npm/ethereum-cryptography@1.1.2, npm/@noble/hashes@1.1.2, npm/@scure/bip32@1.1.0, npm/@scure/bip39@1.1.0, npm/@chainsafe/as-sha256@0.3.1, npm/@chainsafe/persistent-merkle-tree@0.4.2, npm/@chainsafe/ssz@0.9.4, npm/case@1.6.3, npm/bitwise@2.1.0, npm/@ethereumjs/tx@4.1.1, npm/@ethereumjs/common@3.1.1, npm/eth-eip712-util-browser@0.0.3, npm/gridplus-sdk@2.5.1, npm/@scure/base@1.1.7, npm/eth-chainlist@0.0.498

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[danjm]

@SocketSecurity ignore-all

This returns these dependencies to the state they were in on v12.6.2, and these issues are fixed in develop

[metamaskbot]

Builds ready [02ff1ab]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (2079 ± 90 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	405	2494	2002	412	198
		domContentLoaded	1734	2421	2040	179	86
		load	1803	2499	2079	187	90
		domInteractive	28	120	56	25	12
		backgroundConnect	9	104	33	28	13
		firstReactRender	54	298	115	49	23
		getState	5	285	38	60	29
		initialActions	0	1	0	0	0
		loadScripts	1273	1931	1516	167	80
		setupStore	12	104	33	27	13
		uiStartup	1988	2910	2340	245	117