Feat: support OneKey Hardware

[ByteZhang1024]

Description

This pull request adds support for connecting OneKey hardware wallets to the extension.
eth-onekey-bridge-keyring

Related issues

Fixes:

Manual testing steps

1. Plug in a OneKey hardware wallet.
2. Open the MetaMask extension and navigate to the "Connect Hardware Wallet" section.
3. Select "OneKey" from the list.
4. Approve the USB permission request if prompted.
5. Ensure the device is detected and connection is established successfully.

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]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	elliptic@​6.5.7
	@​onekeyfe/​cross-inpage-provider-types@​0.0.17
	@​onekeyfe/​cross-inpage-provider-events@​0.0.17
	@​onekeyfe/​cross-inpage-provider-errors@​0.0.17
	@​onekeyfe/​hd-shared@​1.0.27-alpha.0
	@​onekeyfe/​cross-inpage-provider-core@​0.0.17
	@​babel/​code-frame@​7.25.9
	@​types/​long@​4.0.2
	@​types/​estree@​1.0.7 ⏵ 1.0.6
	eth-onekey-bridge-keyring@​0.2.1
	@​onekeyfe/​hd-transport-http@​1.0.27-alpha.0
	@​onekeyfe/​hd-transport-webusb@​1.0.27-alpha.0
	crc-32@​1.2.0 ⏵ 1.2.2	+1
	bytebuffer@​5.0.1
	safe-stable-stringify@​2.5.0 ⏵ 2.4.3
	socks@​2.8.1
	parse-uri@​1.0.11
	cross-fetch@​3.2.0 ⏵ 3.1.8
	axios@​0.27.2
	detect-browser@​5.2.0
	@​onekeyfe/​hd-transport@​1.0.27-alpha.0
	anymatch@​3.1.2
	node-gyp-build@​4.8.0
	@​onekeyfe/​hd-web-sdk@​1.0.27-alpha.0
	@​onekeyfe/​hd-core@​1.0.27-alpha.0
	base-x@​3.0.11 ⏵ 3.0.10		-15
	@​ngraveio/​bc-ur@​1.1.13 ⏵ 1.1.12

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		[email protected] has a Critical CVE. CVE: GHSA-vjh7-7g9h-fjfh Elliptic's private key extraction in ECDSA upon signing a malformed input (e.g. a string) (CRITICAL) Affected versions: <= 6.6.0 Patched version: 6.6.1 From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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 [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has a High CVE. CVE: GHSA-xq7p-g2vc-g82p Homograph attack allows Unicode lookalike characters to bypass validation. (HIGH) Affected versions: <= 3.0.10 Patched version: 3.0.11 From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is a CVE? Next steps: 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 [email protected]. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Low CVE. CVE: GHSA-fc9h-whq2-v747 Valid ECDSA signatures erroneously rejected in Elliptic (LOW) Affected versions: < 6.6.0 Patched version: 6.6.0 From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is a mild CVE? Next steps: 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 [email protected]. Suggestion: Remove or replace dependencies that include known low severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report