chore(deps): lockbump @metask/eth-sig-util to 6.0.2 and 7.0.1

[legobeat]

• Bump lockfile resolution of @metamask/eth-sig-util@^6.0.0 to 6.0.2
• Bump lockfile resolution of @metamask/eth-sig-util@^7.0.0 to 7.0.1

Related npm audit deprecation for 6.0.1 and 7.0.0:

   ├─ Issue: This version generates invalid signatures for messages that include the value "0x" in a "bytes" field. This has been fixed in v6.0.2 and v7.0.1
   ├─ Severity: moderate
   ├─ Vulnerable Versions: 7.0.0
   │
   ├─ Tree Versions
   │  └─ 7.0.0
   │
   └─ Dependents
      └─ @metamask/eth-json-rpc-middleware@npm:12.0.1

Related issues

• Resolves [Bug]: ethers signTypedData returns incorrect signature / recovered address #7792
  • See also fix: Fix eth_signTypedData signatures containing 0x #7886
• deps: lockbump @metask/eth-sig-util to 6.0.2 and 7.0.1 metamask-extension#21928
• fix: interpret 0x as hex in bytes encodeField eth-sig-util#354
• Update eth_signTypedData_v4 example test-dapp#274

Manual testing steps

[...]

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• 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.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

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]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
New author	@metamask/eth-sig-util	6.0.2	New Author: lgbot Previous Author: metamaskbot	@metamask/keyring-controller@6.1.0 via package.json
Unstable ownership	@metamask/eth-sig-util	6.0.2	Author: lgbot	@metamask/keyring-controller@6.1.0 via package.json

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What is unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore @metamask/eth-sig-util@6.0.2

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (025b627) 37.39% compared to head (a190b39) 37.39%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7902   +/-   ##
=======================================
  Coverage   37.39%   37.39%           
=======================================
  Files        1052     1052           
  Lines       28173    28173           
  Branches     2517     2517           
=======================================
  Hits        10534    10534           
  Misses      17040    17040           
  Partials      599      599           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ElvisKrop]

Hello guys 👋
Please merge this PR asap, we really need this deps update 🙏
Thanks in advance!

[legobeat]

• Merged as part of fix: Fix eth_signTypedData signatures containing 0x #7886