release: 13.36.0

[metamaskbot]

🚀 v13.36.0 Testing & Release Quality Process

Hi Team,
As part of our new MetaMask Release Quality Process, here’s a quick overview of the key processes, testing strategies, and milestones to ensure a smooth and high-quality deployment.

---

📋 Key Processes

Testing Strategy

• Developer Teams:
  Conduct regression and exploratory testing for your functional areas, including automated and manual tests for critical workflows.
• QA Team:
  Focus on exploratory testing across the wallet, prioritize high-impact areas, and triage any Sentry errors found during testing.
• Customer Success Team:
  Validate new functionalities and provide feedback to support release monitoring.

GitHub Signoff

• Each team must sign off on the Release Candidate (RC) via GitHub by the end of the validation timeline (Tuesday EOD PT).
• Ensure all tests outlined in the Testing Plan are executed, and any identified issues are addressed.

Issue Resolution

• Resolve all Release Blockers (Sev0 and Sev1) by Tuesday EOD PT.
• For unresolved blockers, PRs may be reverted, or feature flags disabled to maintain release quality and timelines.

Cherry-Picking Criteria

• Only critical fixes meeting outlined criteria will be cherry-picked.
• Developers must ensure these fixes are thoroughly reviewed, tested, and merged by Tuesday EOD PT.

---

🗓️ Timeline and Milestones

1. Today (Friday): Begin Release Candidate validation.
2. Tuesday EOD PT: Finalize RC with all fixes and cherry-picks.
3. Wednesday: Buffer day for final checks.
4. Thursday: Submit release to app stores and begin rollout to 1% of users.
5. Monday: Scale deployment to 10%.
6. Tuesday: Full rollout to 100%.

---

✅ Signoff Checklist

Each team is responsible for signing off via GitHub. Use the checkbox below to track signoff completion:

Team sign-off checklist

• Extension Platform

This process is a major step forward in ensuring release stability and quality. Let’s stay aligned and make this release a success! 🚀

Feel free to reach out if you have questions or need clarification.

Many thanks in advance

Reference

• Testing plan sheet - https://docs.google.com/spreadsheets/d/1tsoodlAlyvEUpkkcNcbZ4PM9HuC9cEM80RZeoVv5OCQ/edit?gid=404070372#gid=404070372

[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
	@​metamask/​wallet@​2.0.0
	@​metamask/​compliance-controller@​2.1.0
	@​metamask/​snap-account-service@​0.1.0 ⏵ 0.3.0	+1		+1	+3
	@​types/​react-dom@​18.2.0
	@​metamask/​eth-qr-keyring@​2.0.2 ⏵ 2.1.0			+1	+1
	@​metamask/​skills@​0.1.0
	@​metamask/​client-mcp-core@​0.4.0 ⏵ 0.5.0	+1		+1	+1
	@​metamask/​remote-feature-flag-controller@​4.2.1 ⏵ 4.2.2	+1		+1	+3
	@​metamask/​multichain-network-controller@​3.1.2 ⏵ 3.1.3	+1			+2
	@​metamask/​assets-controller@​8.1.0 ⏵ 8.3.2	+7		+1	+1
	@​metamask/​design-system-shared@​0.17.0 ⏵ 0.21.0			+1	+1
	@​metamask/​controller-utils@​12.1.0 ⏵ 12.2.0			+1	+4
	@​metamask/​core-backend@​6.3.1 ⏵ 6.3.2	+2			+1
	@​metamask/​seedless-onboarding-controller@​9.0.0 ⏵ 10.0.1	+2		+1
	@​metamask/​account-tree-controller@​7.3.0 ⏵ 7.5.1	+1		+1
	@​metamask/​bridge-status-controller@​72.0.2
	@​types/​react@​17.0.85 ⏵ 18.2.0	+1		+2
	@​metamask/​bridge-controller@​72.0.0 ⏵ 73.2.0	-7		+1	+1
	@​metamask/​multichain-account-service@​8.0.1 ⏵ 10.0.2	+1			+2
	@​metamask/​design-system-react@​0.22.0 ⏵ 0.25.0			+1	+1
	psl@​1.9.0 ⏵ 1.15.0
	@​metamask/​perps-controller@​6.3.0 ⏵ 8.1.0	+13		+1	+2
	@​metamask/​transaction-controller@​66.0.0 ⏵ 67.0.0
	@​metamask/​bitcoin-wallet-snap@​1.11.0 ⏵ 1.12.0	+1		+1	+1
	core-js-pure@​3.41.0 ⏵ 3.49.0	+1		+1	+1
	@​metamask/​analytics-controller@​1.1.1
	@​metamask/​eth-ledger-bridge-keyring@​12.0.3 ⏵ 12.1.0	+1		+1	+1
	@​metamask/​design-system-tailwind-preset@​0.8.0 ⏵ 0.9.0				+2
	@​metamask/​assets-controllers@​106.0.0 ⏵ 108.5.0	+1		+1
	html-bundler-webpack-plugin@​4.22.0 ⏵ 4.23.2			+1
	@​metamask/​design-tokens@​8.4.0 ⏵ 8.5.0				+1
	@​metamask/​eth-trezor-keyring@​10.0.2 ⏵ 10.1.0	+1		+1	+1
See 2 more rows in the dashboard

View full report

[socket-security]

Caution

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Obfuscated code: npm caniuse-lite is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/autoprefixer@10.4.19 → npm/stylelint@13.6.1 → npm/browserslist@4.28.1 → npm/caniuse-lite@1.0.30001793 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001793. 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		Obfuscated code: npm caniuse-lite is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/autoprefixer@10.4.19 → npm/stylelint@13.6.1 → npm/browserslist@4.28.1 → npm/caniuse-lite@1.0.30001793 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001793. 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		Obfuscated code: npm caniuse-lite is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/autoprefixer@10.4.19 → npm/stylelint@13.6.1 → npm/browserslist@4.28.1 → npm/caniuse-lite@1.0.30001793 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001793. 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		Obfuscated code: npm caniuse-lite is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/autoprefixer@10.4.19 → npm/stylelint@13.6.1 → npm/browserslist@4.28.1 → npm/caniuse-lite@1.0.30001793 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001793. 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		Network access: npm @metamask/bridge-controller in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: package.json → npm/@metamask/bridge-controller@73.2.0 ℹ Read more on: This package | This alert | What is network access? 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 support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/bridge-controller@73.2.0. 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		Network access: npm @metamask/compliance-controller in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: package.json → npm/@metamask/compliance-controller@2.1.0 ℹ Read more on: This package | This alert | What is network access? 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 support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/compliance-controller@2.1.0. 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		Potential code anomaly (AI signal): npm @grpc/grpc-js is 100.0% likely to have a medium risk anomaly Notes: The analyzed fragment is a conventional gRPC subchannel implementation featuring state management, connection orchestration, call creation with optional stats, and credential access delegation. No malicious behavior, backdoors, or data exfiltration patterns are evident in this snippet. Observability through health watchers is limited, which could reduce runtime visibility in some deployments, but does not imply security risk by itself. Confidence: 1.00 Severity: 0.60 From: ? → npm/@metamask/notification-services-controller@23.1.0 → npm/@grpc/grpc-js@1.14.4 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@grpc/grpc-js@1.14.4. 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		Potential code anomaly (AI signal): npm @metamask/client-mcp-core is 100.0% likely to have a medium risk anomaly Notes: This module itself shows no direct indicators of overt malware (no remote exfiltration, no obfuscated payloads, no eval-based code execution). However, it has a significant security trust boundary: it starts an automation daemon by spawning executables resolved from the target project’s configuration (including project-local node_modules/.bin launchers) and then forwards high-privilege automation instructions (clipboard, navigation, CDP, run-steps JSON) to that daemon. If an attacker can influence the chosen worktree/config/daemon state, the risk is elevated to a potential supply-chain/abuse scenario and should be reviewed/mitigated (e.g., restrict project targeting, validate config/daemon paths, and ensure daemon state integrity). Confidence: 1.00 Severity: 0.60 From: package.json → npm/@metamask/client-mcp-core@0.5.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/client-mcp-core@0.5.0. 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		Potential code anomaly (AI signal): npm @metamask/transaction-controller is 100.0% likely to have a medium risk anomaly Notes: The code performs straightforward signature verification using ethers.js, returning true when the recovered signer matches the provided publicKey. While generally safe, the silent catch and potential mismatch between data formatting and signing process should be addressed to avoid silent failures. Overall, a benign utility with moderate input-format sensitivity. Confidence: 1.00 Severity: 0.60 From: ? → npm/@metamask/shield-controller@5.0.1 → npm/@metamask/transaction-controller@62.22.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/transaction-controller@62.22.0. 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		Potential code anomaly (AI signal): npm @metamask/transaction-controller is 100.0% likely to have a medium risk anomaly Notes: The code performs straightforward signature verification using ethers.js, returning true when the recovered signer matches the provided publicKey. While generally safe, the silent catch and potential mismatch between data formatting and signing process should be addressed to avoid silent failures. Overall, a benign utility with moderate input-format sensitivity. Confidence: 1.00 Severity: 0.60 From: ? → npm/@metamask/subscription-controller@6.1.2 → npm/@metamask/user-operation-controller@41.2.0 → npm/@metamask/eip-5792-middleware@3.0.3 → npm/@metamask/profile-metrics-controller@3.1.3 → npm/@metamask/transaction-controller@64.4.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/transaction-controller@64.4.0. 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		Potential code anomaly (AI signal): npm @metamask/transaction-controller is 100.0% likely to have a medium risk anomaly Notes: The code performs straightforward signature verification using ethers.js, returning true when the recovered signer matches the provided publicKey. While generally safe, the silent catch and potential mismatch between data formatting and signing process should be addressed to avoid silent failures. Overall, a benign utility with moderate input-format sensitivity. Confidence: 1.00 Severity: 0.60 From: ? → npm/@metamask/phishing-controller@17.2.0 → npm/@metamask/smart-transactions-controller@24.2.0 → npm/@metamask/transaction-controller@65.4.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/transaction-controller@65.4.0. 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		Potential code anomaly (AI signal): npm @metamask/transaction-controller is 100.0% likely to have a medium risk anomaly Notes: The code performs straightforward signature verification using ethers.js, returning true when the recovered signer matches the provided publicKey. While generally safe, the silent catch and potential mismatch between data formatting and signing process should be addressed to avoid silent failures. Overall, a benign utility with moderate input-format sensitivity. Confidence: 1.00 Severity: 0.60 From: ? → npm/@metamask/transaction-pay-controller@22.6.0 → npm/@metamask/gator-permissions-controller@4.2.0 → npm/@metamask/bridge-controller@73.2.0 → npm/@metamask/assets-controllers@108.5.0 → npm/@metamask/assets-controller@8.3.2 → npm/@metamask/bridge-status-controller@72.0.2 → npm/@metamask/network-enablement-controller@5.3.0 → npm/@metamask/transaction-controller@66.0.1 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/transaction-controller@66.0.1. 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		Potential code anomaly (AI signal): npm @metamask/transaction-controller is 100.0% likely to have a medium risk anomaly Notes: The code performs straightforward signature verification using ethers.js, returning true when the recovered signer matches the provided publicKey. While generally safe, the silent catch and potential mismatch between data formatting and signing process should be addressed to avoid silent failures. Overall, a benign utility with moderate input-format sensitivity. Confidence: 1.00 Severity: 0.60 From: package.json → npm/@metamask/transaction-controller@67.0.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/transaction-controller@67.0.0. 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		Potential code anomaly (AI signal): npm caniuse-lite is 100.0% likely to have a medium risk anomaly Notes: This fragment is purely static exported data (an encoded/token lookup table plus metadata). It contains no direct malicious actions in isolation (no DOM/network/filesystem access and no executable behavior), but the explicit metadata referencing DOM media capture and the cipher-like token table structure are meaningful indicators that other parts of the package may implement privacy-invasive capture and potentially related processing/exfiltration. Review the consuming modules for actual media API usage and any handling/transmission of captured content. Confidence: 1.00 Severity: 0.60 From: ? → npm/autoprefixer@10.4.19 → npm/stylelint@13.6.1 → npm/browserslist@4.28.1 → npm/caniuse-lite@1.0.30001793 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001793. 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		Potential code anomaly (AI signal): npm core-js-pure is 100.0% likely to have a medium risk anomaly Notes: The fragment implements a conventional abstract AsyncIterator polyfill pattern. It prevents direct construction, attaches type metadata, and exposes AsyncIteratorConstructor globally in a controlled manner. There are no signs of data exfiltration, external I/O, or hidden behavior. Overall security risk is low, malware likelihood is negligible in this fragment, and the code aligns with legitimate library usage (e.g., core-js style shims). Confidence: 1.00 Severity: 0.60 From: package.json → npm/core-js-pure@3.49.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/core-js-pure@3.49.0. 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		Potential code anomaly (AI signal): npm html-bundler-webpack-plugin is 100.0% likely to have a medium risk anomaly Notes: The code is a thin wrapper around vm.Script and is not itself obfuscated or demonstrably malicious. However it is inherently risky: it executes arbitrary code strings in a vm context that inherits any objects supplied by the caller. If untrusted code or an unsafe context is used, this can lead to arbitrary code execution, data leakage, or access to OS resources. Mitigations would be to ensure contexts do not contain host capabilities, add execution time/memory limits, and validate or sandbox inputs. No hardcoded secrets or obvious backdoors were found in this fragment. Confidence: 1.00 Severity: 0.60 From: package.json → npm/html-bundler-webpack-plugin@4.23.2 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/html-bundler-webpack-plugin@4.23.2. 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

[metamaskbotv2]

Builds ready [f6fe718]

• ⚠️ Make sure the build is safe before downloading and running this build.
  • Please do not use these builds with accounts that contain significant real money.
  • Beware the security risks of cache poisoning.
• Webpack builds: chrome, firefox
• Webpack builds (beta): chrome, firefox
• Webpack builds (flask): chrome, firefox
• Webpack builds (test): chrome, firefox
• Webpack builds (test-flask): chrome, firefox
• bundle size: Bundle Size Stats
• bundle analyzer: Bundle Analyzer
• interaction-benchmark: Interaction Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts

Deprecated Browserify fallback builds

• Browserify builds: chrome, firefox
• Browserify builds (beta): chrome, firefox
• Browserify builds (flask): chrome, firefox
• Browserify builds (test): chrome, firefox
• Browserify builds (test-flask): chrome, firefox

⚡ Performance Benchmarks (Total: 🟢 9 pass · 🟡 13 warn · 🔴 3 fail)

Baseline (latest main): f6fe718 | Date: 6/11/2026 | Pipeline: 27371365979 | Baseline logs

Metrics	chrome-webpack	firefox-webpack
onboardingImportWallet [Sentry log · main/release]	🔴 doneButtonToHomeScreen(p95) [CI log]	🔴 [CI log]
onboardingNewWallet [Sentry log · main/release]	🟢 [CI log]	🔴 [CI log]

Regressions (🔴 3 failures)

• onboardingImportWallet [Sentry log · main/release] · chrome-webpack — total(p95) [CI log]
• onboardingImportWallet [Sentry log · main/release] · firefox-webpack — total(p75) [CI log]
• onboardingNewWallet [Sentry log · main/release] · firefox-webpack — total(p75) [CI log]

Interaction Benchmarks · Samples: 5

Benchmark	chrome-webpack	firefox-webpack
loadNewAccount [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]
confirmTx [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]
bridgeUserActions [Sentry log · main/release]	🟡 [CI log]	🟢 [CI log]

📈 Results compared to the previous 5 runs on main

• ↓ loadNewAccount/inp: -31%
• ↑ loadNewAccount/lcp: +18%
• ↑ confirmTx/longTaskMaxDuration: +14%
• ↑ confirmTx/tbt: +21%
• ↑ confirmTx/inp: +12%
• ↑ bridgeUserActions/bridge_load_asset_picker: +19%
• ↑ bridgeUserActions/longTaskCount: +67%
• ↑ bridgeUserActions/longTaskTotalDuration: +52%
• ↑ bridgeUserActions/tbt: +14%
• ↓ bridgeUserActions/inp: -11%
• ↑ loadNewAccount/load_new_account: +59%
• ↑ loadNewAccount/total: +59%
• ↓ loadNewAccount/inp: -31%
• ↓ loadNewAccount/fcp: -49%
• ↑ loadNewAccount/lcp: +1368%
• ↑ confirmTx/confirm_tx: +12%
• ↓ confirmTx/longTaskCount: -100%
• ↓ confirmTx/longTaskTotalDuration: -100%
• ↓ confirmTx/longTaskMaxDuration: -100%
• ↓ confirmTx/tbt: -100%
• ↑ confirmTx/total: +12%
• ↑ confirmTx/inp: +12%
• ↑ confirmTx/fcp: +10%
• ↑ confirmTx/lcp: +1269%
• ↑ bridgeUserActions/bridge_load_page: +237%
• ↑ bridgeUserActions/bridge_load_asset_picker: +40%
• ↑ bridgeUserActions/bridge_search_token: +11%
• ↓ bridgeUserActions/longTaskCount: -100%
• ↓ bridgeUserActions/longTaskTotalDuration: -100%
• ↓ bridgeUserActions/longTaskMaxDuration: -100%
• ↓ bridgeUserActions/tbt: -100%
• ↑ bridgeUserActions/total: +25%
• ↓ bridgeUserActions/inp: -26%
• ↓ bridgeUserActions/fcp: -51%
• ↑ bridgeUserActions/lcp: +1200%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🟡 loadNewAccount/FCP: p75 1.9s
• 🟡 confirmTx/FCP: p75 1.8s
• 🟡 bridgeUserActions/FCP: p75 1.8s
• 🟡 loadNewAccount/LCP: p75 2.5s
• 🟡 confirmTx/FCP: p75 1.9s

Startup Benchmarks · Samples: 100

Benchmark	chrome-webpack	firefox-webpack
startupStandardHome [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
startupPowerUserHome [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]

📈 Results compared to the previous 5 runs on main

• ↓ startupPowerUserHome/setupStore: -18%
• ↓ startupPowerUserHome/numNetworkReqs: -14%
• ↓ startupPowerUserHome/longTaskCount: -14%
• ↑ startupStandardHome/domInteractive: +13%
• ↑ startupStandardHome/fcp: +16%
• ↓ startupPowerUserHome/domInteractive: -23%
• ↓ startupPowerUserHome/backgroundConnect: -49%
• ↓ startupPowerUserHome/setupStore: -19%
• ↓ startupPowerUserHome/fcp: -21%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🟡 startupPowerUserHome/INP: p75 480ms
• 🟡 startupPowerUserHome/LCP: p75 2.6s

User Journey Benchmarks · Samples: 5 · real API 🔴 3

Benchmark	chrome-webpack	firefox-webpack
onboardingImportWallet [Sentry log · main/release]	🔴 [CI log] 🔴 doneButtonToHomeScreen 🔴 total	🔴 [CI log] 🟡 doneButtonToHomeScreen 🔴 total
onboardingNewWallet [Sentry log · main/release]	🟢 [CI log]	🔴 [CI log] 🔴 total
assetDetails [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
solanaAssetDetails [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]
importSrpHome [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]
sendTransactions [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]
swap [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]

📈 Results compared to the previous 5 runs on main

• ↓ onboardingImportWallet/confirmSrpToPwForm: -13%
• ↑ onboardingImportWallet/doneButtonToHomeScreen: +33%
• ↓ onboardingImportWallet/openAccountMenuToAccountListLoaded: -28%
• ↑ onboardingImportWallet/longTaskCount: +14%
• ↑ onboardingImportWallet/longTaskTotalDuration: +25%
• ↑ onboardingImportWallet/longTaskMaxDuration: +22%
• ↑ onboardingImportWallet/tbt: +16%
• ↑ onboardingImportWallet/total: +26%
• ↑ onboardingNewWallet/longTaskTotalDuration: +14%
• ↑ onboardingNewWallet/longTaskMaxDuration: +20%
• ↑ onboardingNewWallet/tbt: +20%
• ↑ solanaAssetDetails/assetClickToPriceChart: +81%
• ↑ solanaAssetDetails/total: +81%
• ↑ solanaAssetDetails/cls: +23%
• ↓ importSrpHome/openAccountMenuAfterLogin: -18%
• ↓ importSrpHome/inp: -18%
• ↓ sendTransactions/selectTokenToSendFormLoaded: -14%
• ↑ sendTransactions/longTaskCount: +25%
• ↑ sendTransactions/longTaskTotalDuration: +18%
• ↑ sendTransactions/tbt: +13%
• ↓ sendTransactions/lcp: -10%
• ↓ sendTransactions/cls: -73%
• ↑ swap/openSwapPageFromHome: +66%
• ↑ swap/longTaskMaxDuration: +16%
• ↑ swap/tbt: +12%
• ↓ swap/cls: -30%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🟡 importSrpHome/INP: p75 232ms
• 🟡 sendTransactions/INP: p75 208ms
• 🟡 solanaAssetDetails/FCP: p75 2.0s
• 🟡 importSrpHome/FCP: p75 1.9s
• 🟡 sendTransactions/FCP: p75 2.0s
• 🟡 swap/FCP: p75 1.9s

Dapp Page Load Benchmarks · Samples: 100

Benchmark	chrome-webpack
dappPageLoad [Sentry log · main/release]	🟢 [CI log]

Bundle size diffs

• background: 113 Bytes (0%)
• ui: 10 Bytes (0%)
• common: 40 Bytes (0%)

AI Test Plan

Risk Score	High Risk	Medium Risk	Files Changed	Commits
46/100	4	5	1588	109

Release Scenarios (9)

High Risk Scenarios (4)

1. State Migrations (212, 213) – upgrade path/data integrity

Risk Level: HIGH

Why This Matters: Migrations can corrupt or drop critical user data (accounts, assets, networks) and break pending transactions after upgrade.

Test Steps:

1. On 13.35.x create a profile with: 2 accounts (one imported), add a custom RPC network, add 2 custom ERC-20s and 1 NFT, connect a dapp, and leave 1 tx pending.
2. Update to 13.36.0, unlock, and allow migrations to complete.
3. Verify accounts, custom network, tokens, NFTs, and connected site persist; balances render without errors.
4. Confirm the pending tx is present and actionable (can Speed up/Cancel and completes correctly).
5. Check Settings > Security & privacy: MetaMetrics preference preserved (no unexpected re-prompt).

---

2. Token/NFT Management – Assets Controller upgrade (8.3.x)

Risk Level: HIGH

Why This Matters: Upgrading the Assets controller and related selectors can change how token/NFT metadata is resolved, risking wrong symbols/logos, missing assets, or cross-chain confusion.

Test Steps:

1. On Ethereum Mainnet enable Token autodetection, then receive a popular token (e.g., USDC) and verify symbol/decimals/logo and fiat conversion are correct.
2. Manually add a custom token by contract address; verify metadata and balance, then Hide/Unhide and ensure it persists across reload.
3. On a non-mainnet EVM (e.g., Polygon), repeat: autodetection on, receive a known token, confirm correct logo/metadata and no cross-chain mix-ups.
4. In the NFT tab, import an NFT by contract/token ID; verify image loads in Assets and in the Activity entry after a transfer.

---

3. Transaction Sending – Gas estimation and editing (Transaction Pay Controller patch)

Risk Level: HIGH

Why This Matters: Controller changes around gas/payment can cause wrong fee types, failed sends, or inability to edit fees across EIP-1559 vs legacy networks.

Test Steps:

1. On Ethereum Mainnet send ETH; open Edit gas > Advanced and set custom Max fee and Priority fee; confirm the tx and ensure it is mined.
2. On a legacy-gas network (e.g., BNB Smart Chain or a custom legacy RPC), send a token; verify only Gas price is shown, edit it, and confirm success.
3. Attempt a send with near-zero balance to trigger 'insufficient funds' and confirm the Confirm button is blocked with clear error messaging.
4. From the Activity list, Speed up a pending tx and verify the replacement tx is created with updated fee and the original is replaced.

---

4. Pending Transactions Survivability Across Upgrade

Risk Level: HIGH

Why This Matters: State model changes can break pending tx tracking, causing stuck states or lost replacement actions.

Test Steps:

1. On 13.35.x submit a low-fee tx to keep it pending.
2. Upgrade to 13.36.0 and unlock; open Activity and locate the pending item.
3. Use Cancel to replace-with-cancel; verify status updates and the original is dropped.
4. Submit another pending tx and then Speed up; verify the replacement confirms and final status is correct.

---

Medium Risk Scenarios (5)

1. Activity List – Avatars and transaction type icons

Risk Level: MEDIUM

Why This Matters: Avatar component refactor can regress core visual cues in the Activity feed, confusing users about what happened and with which asset.

Test Steps:

1. Perform: Send ETH, Swap a token, and Transfer an NFT; ensure each Activity item shows the correct avatar (token logo/NFT thumbnail) and direction labels.
2. Simulate an incoming transfer (from another wallet) and verify the received item shows the correct token icon and 'Received' labeling.
3. Open each Activity detail; verify avatars and token/NFT metadata match the summary item and no placeholders or broken images appear.

---

2. Alert Modal – Destructive action confirmations

Risk Level: MEDIUM

Why This Matters: Alert modal changes affect confirmation and cancellation flows; regressions can cause unintended destructive actions or traps.

Test Steps:

1. Import a private key account, then attempt to Remove it; review the alert modal’s copy and primary/secondary button states.
2. Cancel the modal via the Cancel button and via clicking the overlay/Esc; verify no account is removed and no side effects occur.
3. Re-open and Confirm removal; verify the account is removed and the UI returns to a valid state without errors.

---

3. Account List – Selection and identity display

Risk Level: MEDIUM

Why This Matters: Account list item changes can break switching, labeling, and accessibility, directly impacting core wallet navigation.

Test Steps:

1. Open the account menu with multiple accounts; select different accounts and verify the active state/checkmark and balance update everywhere.
2. Rename an account and ensure the new label appears in the account list and Activity immediately (no stale cache).
3. With many accounts, scroll and select via keyboard (Up/Down + Enter) to ensure focus/selection works and no clipping or mis-clicks.

---

4. MetaMetrics Consent – Onboarding and settings toggle (Platform analytics adapter)

Risk Level: MEDIUM

Why This Matters: New analytics platform adapter and event type changes risk consent state regressions or silent event emission when opted out.

Test Steps:

1. Fresh install: go through onboarding choosing 'No thanks' for MetaMetrics; open Settings > Security & privacy and confirm the toggle is Off.
2. Toggle MetaMetrics On; restart extension and verify the preference persists and no re-prompt appears.
3. New profile: choose 'I agree' during onboarding; confirm no consent re-prompt later and the toggle reflects On.

---

5. Add/Watch Asset (watchAsset) – Token addition and display

Risk Level: MEDIUM

Why This Matters: Selector and assets controller updates can break watchAsset flows, causing missing or cross-chain misassigned tokens.

Test Steps:

1. From a test dapp, call wallet_watchAsset to add a token; accept in the extension and verify it appears with correct metadata and logo.
2. Hide the watched token and unhide it from the Hidden assets view; ensure state persists after reload.
3. Switch networks and ensure the watched token is only visible on the correct chain (no cross-network leakage).

---

Teams Sign-off Status

Signed off: None yet

Awaiting sign-off (6):
Accounts, Assets, Confirmations, Onboarding, Settings, Transactions

---

Generated by AI Test Plan Analyzer (gpt-5) at 2026-06-11T19:44:50.873Z

AI generated test plan (JSON): test-plan-13.36.0.json

[metamaskbotv2]

Builds ready [b35e9e7]

• ⚠️ Make sure the build is safe before downloading and running this build.
  • Please do not use these builds with accounts that contain significant real money.
  • Beware the security risks of cache poisoning.
• Webpack builds: chrome, firefox
• Webpack builds (beta): chrome, firefox
• Webpack builds (flask): chrome, firefox
• Webpack builds (test): chrome, firefox
• Webpack builds (test-flask): chrome, firefox
• bundle size: Bundle Size Stats
• bundle analyzer: Bundle Analyzer
• interaction-benchmark: Interaction Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts

Deprecated Browserify fallback builds

• Browserify builds: chrome, firefox
• Browserify builds (beta): chrome, firefox
• Browserify builds (flask): chrome, firefox
• Browserify builds (test): chrome, firefox
• Browserify builds (test-flask): chrome, firefox

⚡ Performance Benchmarks (Total: 🟢 15 pass · 🟡 7 warn · 🔴 3 fail)

Baseline (latest main): 5682526 | Date: 6/13/2026 | Pipeline: 27457742824 | Baseline logs

Metrics	chrome-webpack	firefox-webpack
onboardingImportWallet [Sentry log · main/release]	🔴 confirmSrpToPwForm(p95) [CI log]	🔴 [CI log]
onboardingNewWallet [Sentry log · main/release]	🟢 [CI log]	🔴 [CI log]

Regressions (🔴 3 failures)

• onboardingImportWallet [Sentry log · main/release] · chrome-webpack — total(p95) [CI log]
• onboardingImportWallet [Sentry log · main/release] · firefox-webpack — total(p75) [CI log]
• onboardingNewWallet [Sentry log · main/release] · firefox-webpack — total(p75) [CI log]

Interaction Benchmarks · Samples: 5

Benchmark	chrome-webpack	firefox-webpack
loadNewAccount [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
confirmTx [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
bridgeUserActions [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]

📈 Results compared to the previous 5 runs on main

• ↑ loadNewAccount/load_new_account: +24%
• ↑ loadNewAccount/total: +24%
• ↓ loadNewAccount/lcp: -21%
• ↑ confirmTx/inp: +10%
• ↓ bridgeUserActions/bridge_load_page: -36%
• ↑ loadNewAccount/load_new_account: +91%
• ↑ loadNewAccount/total: +91%
• ↑ loadNewAccount/lcp: +1050%
• ↑ confirmTx/confirm_tx: +11%
• ↓ confirmTx/longTaskCount: -100%
• ↓ confirmTx/longTaskTotalDuration: -100%
• ↓ confirmTx/longTaskMaxDuration: -100%
• ↓ confirmTx/tbt: -100%
• ↑ confirmTx/total: +11%
• ↓ confirmTx/inp: -10%
• ↑ confirmTx/lcp: +1079%
• ↑ bridgeUserActions/bridge_load_page: +67%
• ↑ bridgeUserActions/bridge_load_asset_picker: +79%
• ↑ bridgeUserActions/bridge_search_token: +28%
• ↓ bridgeUserActions/longTaskCount: -100%
• ↓ bridgeUserActions/longTaskTotalDuration: -100%
• ↓ bridgeUserActions/longTaskMaxDuration: -100%
• ↓ bridgeUserActions/tbt: -100%
• ↑ bridgeUserActions/total: +53%
• ↓ bridgeUserActions/inp: -32%
• ↓ bridgeUserActions/fcp: -50%
• ↑ bridgeUserActions/lcp: +1143%

Startup Benchmarks · Samples: 100

Benchmark	chrome-webpack	firefox-webpack
startupStandardHome [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
startupPowerUserHome [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]

📈 Results compared to the previous 5 runs on main

• ↑ startupPowerUserHome/setupStore: +10%
• ↓ startupPowerUserHome/numNetworkReqs: -30%
• ↑ startupPowerUserHome/tbt: +10%
• ↓ startupPowerUserHome/backgroundConnect: -19%
• ↑ startupPowerUserHome/setupStore: +13%
• ↓ startupPowerUserHome/numNetworkReqs: -19%
• ↓ startupPowerUserHome/inp: -12%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🔴 startupPowerUserHome/INP: p75 536ms
• 🟡 startupPowerUserHome/LCP: p75 2.9s

User Journey Benchmarks · Samples: 5 · real API 🔴 3

Benchmark	chrome-webpack	firefox-webpack
onboardingImportWallet [Sentry log · main/release]	🔴 [CI log] 🔴 doneButtonToHomeScreen 🔴 total	🔴 [CI log] 🟡 doneButtonToHomeScreen 🔴 total
onboardingNewWallet [Sentry log · main/release]	🟢 [CI log]	🔴 [CI log] 🔴 total
assetDetails [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
solanaAssetDetails [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]
importSrpHome [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]
sendTransactions [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]
swap [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]

📈 Results compared to the previous 5 runs on main

• ↑ onboardingImportWallet/confirmSrpToPwForm: +14%
• ↑ onboardingImportWallet/doneButtonToHomeScreen: +18%
• ↑ onboardingImportWallet/openAccountMenuToAccountListLoaded: +24%
• ↑ onboardingImportWallet/total: +49%
• ↓ onboardingNewWallet/srpButtonToPwForm: -22%
• ↓ onboardingNewWallet/createPwToRecoveryScreen: -23%
• ↓ onboardingNewWallet/skipBackupToMetricsScreen: -19%
• ↓ onboardingNewWallet/agreeButtonToOnboardingSuccess: -17%
• ↓ onboardingNewWallet/doneButtonToAssetList: -24%
• ↓ onboardingNewWallet/longTaskCount: -55%
• ↓ onboardingNewWallet/longTaskTotalDuration: -59%
• ↓ onboardingNewWallet/longTaskMaxDuration: -30%
• ↓ onboardingNewWallet/tbt: -66%
• ↓ onboardingNewWallet/total: -22%
• ↑ solanaAssetDetails/assetClickToPriceChart: +36%
• ↓ solanaAssetDetails/longTaskCount: -100%
• ↓ solanaAssetDetails/longTaskTotalDuration: -100%
• ↓ solanaAssetDetails/longTaskMaxDuration: -100%
• ↓ solanaAssetDetails/tbt: -100%
• ↑ solanaAssetDetails/total: +36%
• ↓ solanaAssetDetails/lcp: -10%
• ↑ solanaAssetDetails/cls: +20%
• ↓ importSrpHome/loginToHomeScreen: -34%
• ↓ importSrpHome/openAccountMenuAfterLogin: -16%
• ↓ importSrpHome/homeAfterImportWithNewWallet: -18%
• ↓ importSrpHome/longTaskCount: -22%
• ↓ importSrpHome/longTaskTotalDuration: -39%
• ↓ importSrpHome/longTaskMaxDuration: -32%
• ↓ importSrpHome/tbt: -43%
• ↓ importSrpHome/total: -21%
• ↓ importSrpHome/inp: -35%
• ↓ importSrpHome/fcp: -28%
• ↑ sendTransactions/openSendPageFromHome: +18%
• ↑ sendTransactions/selectTokenToSendFormLoaded: +17%
• ↑ sendTransactions/reviewTransactionToConfirmationPage: +15%
• ↑ sendTransactions/longTaskTotalDuration: +30%
• ↑ sendTransactions/tbt: +47%
• ↑ sendTransactions/total: +14%
• ↑ sendTransactions/fcp: +16%
• ↑ sendTransactions/lcp: +17%
• ↓ sendTransactions/cls: -89%
• ↑ swap/fetchAndDisplaySwapQuotes: +38%
• ↑ swap/longTaskCount: +67%
• ↑ swap/longTaskTotalDuration: +63%
• ↑ swap/longTaskMaxDuration: +58%
• ↑ swap/tbt: +59%
• ↑ swap/total: +38%
• ↓ swap/lcp: -64%
• ↓ swap/cls: -39%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🟡 sendTransactions/INP: p75 232ms
• 🟡 sendTransactions/FCP: p75 2.0s
• 🟡 solanaAssetDetails/FCP: p75 2.0s
• 🟡 importSrpHome/FCP: p75 1.9s
• 🟡 sendTransactions/FCP: p75 1.9s
• 🟡 swap/FCP: p75 1.9s

Dapp Page Load Benchmarks · Samples: 100

Benchmark	chrome-webpack
dappPageLoad [Sentry log · main/release]	🟢 [CI log]

Bundle size diffs

• background: 113 Bytes (0%)
• ui: 10 Bytes (0%)
• common: 299 Bytes (0%)

AI Test Plan

Risk Score	High Risk	Medium Risk	Files Changed	Commits
62/100	8	6	1587	110

Release Scenarios (14)

High Risk Scenarios (8)

1. State Migrations (migrations 212/213) - Upgrade Path

Risk Level: HIGH

Why This Matters: Two new state migrations can corrupt or drop user data if misapplied; this verifies correctness across core assets, accounts, and preferences.

Test Steps:

1. Install 13.35.x, create a new wallet, add: one imported private key account, rename accounts, set primary currency to fiat, and opt OUT of MetaMetrics.
2. On Ethereum and Polygon, enable token detection, add at least one custom token on each, and ensure at least one ERC-721 NFT is visible (use test collectibles if needed).
3. Upgrade to 13.36.0, unlock wallet, and verify account order, labels, and preferences (currency, MetaMetrics opt-out) are preserved.
4. Verify tokens/NFTs are present exactly once per network, activity history is intact, and there are no migration error banners or crashes.

---

2. State Migrations (older profile edge) - Long-jump Upgrade

Risk Level: HIGH

Why This Matters: Users may upgrade across several versions; chained migrations must compose correctly or risk data loss/duplication.

Test Steps:

1. Start from a significantly older profile (e.g., 13.30.x) with multiple accounts, custom tokens on multiple networks, and NFTs present.
2. Upgrade directly to 13.36.0.
3. Confirm all accounts, labels, and connected sites persist; verify assets and NFTs render correctly without duplication.
4. Open Settings > Advanced and ensure feature flags and detection toggles retain previous values.

---

3. Transaction Sending (EIP-1559) - Transaction Pay Controller

Risk Level: HIGH

Why This Matters: Transaction Pay controller changes can affect fee estimation and transaction lifecycle, risking failed or overpriced transactions.

Test Steps:

1. On an EIP-1559 network (e.g., Ethereum mainnet or Sepolia), send a native token transfer and review the fee UI (suggested, market, advanced).
2. Edit gas settings (max fee and priority fee), submit the transaction, then perform a Speed Up and Cancel on a pending tx.
3. Validate final fees charged and status updates in Activity; ensure fee changes persist and match confirmations.
4. Confirm no stuck pending states or incorrect fee estimates appear after adjustments.

---

4. Dapp-initiated Transactions & Suggested Gas

Risk Level: HIGH

Why This Matters: Ensures controller and UI correctly handle dapp-suggested fees, a common real-world pattern that can break with fee controller changes.

Test Steps:

1. From a connected dapp, initiate a token approval (ERC-20 approve) and a token transfer with dapp-suggested gas values.
2. In the confirmation UI, compare suggested vs. MetaMask estimates; modify fees and submit.
3. Confirm the transactions complete and the final fees charged align with the edited values.
4. Verify no UI freezes or mis-rendered fee sections during dapp confirmations.

---

5. Token Detection & Portfolio (Assets Controller 8.3.2)

Risk Level: HIGH

Why This Matters: Assets Controller upgrade can regress auto-detection, duplication handling, and pricing—core to asset visibility and trust.

Test Steps:

1. On Ethereum and Polygon, enable token detection and verify common tokens auto-appear without duplicates.
2. Disable token detection and confirm no new tokens auto-appear while existing tokens remain.
3. Switch between networks and verify token lists are network-scoped and consistent.
4. Validate fiat pricing appears for known tokens and remains stable across refreshes.

---

6. Add Custom Token (Decimals & Duplicate Handling)

Risk Level: HIGH

Why This Matters: Custom tokens are frequently added; incorrect decimals or duplicate handling can cause incorrect balances and user confusion.

Test Steps:

1. Add a custom ERC-20 by contract address on Network A and verify symbol/decimals are correct.
2. Attempt to re-add the same token; confirm the UI prevents duplication.
3. Switch to Network B and add the same contract (if valid on B) or a different token; ensure network scoping works.
4. Remove then re-add the token and verify balances and history remain unaffected.

---

7. Swaps Flow (Quotes, Fees, and Confirmation)

Risk Level: HIGH

Why This Matters: Fee and transaction handling impacts swaps; regressions may cause failed swaps, incorrect fees, or wrong balances.

Test Steps:

1. Initiate a token-to-token swap on a supported network and review the quotes, slippage, and fee breakdown.
2. Edit slippage and confirm the updated quotes recalculate correctly.
3. Submit the swap and confirm the final status and fees match the confirmation.
4. Check Activity and token balances post-swap for consistency.

---

8. Alert Modal (System-wide) - Network Switch & Removal

Risk Level: HIGH

Why This Matters: Alert modal changes can break global confirmation flows, blocking critical actions like network switching.

Test Steps:

1. From a dapp, trigger wallet_switchEthereumChain and wallet_addEthereumChain requests.
2. In the alert modal, test Cancel and Approve paths; verify network switches/creation reflect immediately in the network selector.
3. Remove a custom network from Settings and confirm the confirmation modal behaves correctly (focus trap, ESC/overlay click handling).
4. Confirm no invisible modals block interaction after dismissal.

---

Medium Risk Scenarios (6)

1. NFT Detection & Display (Avatars/Media Fallbacks)

Risk Level: MEDIUM

Why This Matters: The Assets controller and activity avatar component changes affect NFT visuals; broken media handling degrades UX.

Test Steps:

1. Ensure at least one ERC-721 NFT is detected; check the NFT tab for correct image/media rendering.
2. For an NFT with a broken or slow media URL, verify graceful fallback (initials/icon) without layout shifts.
3. Switch accounts and networks to confirm NFT lists update correctly without leakage across accounts.
4. Open the Activity tab and ensure NFT-related events show the expected avatar/icons.

---

2. Permissions Connect Flow (Alert Modal)

Risk Level: MEDIUM

Why This Matters: Connection approvals rely on the alert modal; regressions can either over-grant or fail to grant permissions.

Test Steps:

1. From a new dapp, request connection; verify the connect modal lists accounts and permissions clearly.
2. Approve connection with one account, then reconnect and approve a second account.
3. Test Deny and ensure the dapp remains disconnected; no phantom connections appear.
4. Verify keyboard navigation and focus remain trapped within the modal until dismissal.

---

3. MetaMetrics Opt-in/Out (New Platform Adapter)

Risk Level: MEDIUM

Why This Matters: New analytics platform adapter can alter event dispatch and privacy guarantees; incorrect handling risks privacy regressions.

Test Steps:

1. Run first-time onboarding and verify the MetaMetrics opt-in prompt appears; choose Opt-out.
2. Perform a basic action (send or account switch) and confirm no MetaMetrics events are sent (inspect background/network logs if available).
3. Toggle MetaMetrics ON in Settings > Security & Privacy; perform the same action and verify events are now sent.
4. Restart the extension and confirm the opt-in preference persists.

---

4. MetaMetrics Data Deletion Request

Risk Level: MEDIUM

Why This Matters: Users must be able to delete telemetry data without breaking analytics preferences or causing errors.

Test Steps:

1. In Settings > Security & Privacy, initiate a MetaMetrics data deletion (if available).
2. Confirm the confirmation flow completes with success feedback and no UI dead-ends.
3. Ensure subsequent actions still function normally and do not crash the extension.
4. Toggle MetaMetrics off/on afterward and confirm the setting still works.

---

5. Activity List Avatars (Transfers, Approvals, Swaps, NFT Events)

Risk Level: MEDIUM

Why This Matters: Avatar component refactor can misclassify or misrender activity icons, harming clarity of transaction history.

Test Steps:

1. Generate different activity types: native send, ERC-20 approval, token transfer, NFT transfer, and a swap.
2. Open Activity and verify each entry shows the correct avatar/icon and label.
3. Click into activity details to ensure the icon matches the transaction type there as well.
4. Switch theme (light/dark) and confirm readability and contrast.

---

6. Account List Item (Selection & Quick Actions)

Risk Level: MEDIUM

Why This Matters: Small account list changes can break core actions like selection and copy, degrading everyday usability.

Test Steps:

1. Open account list and switch accounts; verify the selected state updates immediately across the UI.
2. Copy the address from the list item and confirm the copied value is correct.
3. Rename an account and verify the list updates without duplicates or layout jumps.
4. From a dapp with permissions, switch the active account and ensure the dapp reflects the change.

---

Teams Sign-off Status

Signed off: None yet

Awaiting sign-off (8):
Accounts, Assets, Confirmations, Networks, Permissions, Swaps, Transactions, Wallet Integrations

---

Generated by AI Test Plan Analyzer (gpt-5) at 2026-06-13T05:54:33.582Z

AI generated test plan (JSON): test-plan-13.36.0.json

[metamaskbotv2]

Builds ready [ea759f7]

• ⚠️ Make sure the build is safe before downloading and running this build.
  • Please do not use these builds with accounts that contain significant real money.
  • Beware the security risks of cache poisoning.
• Webpack builds: chrome, firefox
• Webpack builds (beta): chrome, firefox
• Webpack builds (flask): chrome, firefox
• Webpack builds (test): chrome, firefox
• Webpack builds (test-flask): chrome, firefox
• bundle size: Bundle Size Stats
• bundle analyzer: Bundle Analyzer
• interaction-benchmark: Interaction Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts

Deprecated Browserify fallback builds

• Browserify builds: chrome, firefox
• Browserify builds (beta): chrome, firefox
• Browserify builds (flask): chrome, firefox
• Browserify builds (test): chrome, firefox
• Browserify builds (test-flask): chrome, firefox

⚡ Performance Benchmarks (Total: 🟢 15 pass · 🟡 7 warn · 🔴 3 fail)

Baseline (latest main): 5682526 | Date: 6/13/2026 | Pipeline: 27458463242 | Baseline logs

Metrics	chrome-webpack	firefox-webpack
onboardingImportWallet [Sentry log · main/release]	🔴 longTaskTotalDuration(p95) [CI log]	🔴 [CI log]
onboardingNewWallet [Sentry log · main/release]	🟢 [CI log]	🔴 [CI log]

Regressions (🔴 3 failures)

• onboardingImportWallet [Sentry log · main/release] · chrome-webpack — total(p75) [CI log]
• onboardingImportWallet [Sentry log · main/release] · firefox-webpack — total(p75) [CI log]
• onboardingNewWallet [Sentry log · main/release] · firefox-webpack — total(p95) [CI log]

Interaction Benchmarks · Samples: 5

Benchmark	chrome-webpack	firefox-webpack
loadNewAccount [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
confirmTx [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
bridgeUserActions [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]

📈 Results compared to the previous 5 runs on main

• ↑ loadNewAccount/load_new_account: +20%
• ↑ loadNewAccount/total: +20%
• ↓ loadNewAccount/inp: -12%
• ↑ confirmTx/inp: +60%
• ↓ bridgeUserActions/bridge_load_page: -38%
• ↓ bridgeUserActions/longTaskTotalDuration: -22%
• ↓ bridgeUserActions/longTaskMaxDuration: -22%
• ↓ bridgeUserActions/tbt: -49%
• ↑ bridgeUserActions/inp: +14%
• ↑ loadNewAccount/load_new_account: +118%
• ↑ loadNewAccount/total: +118%
• ↓ loadNewAccount/inp: -12%
• ↓ loadNewAccount/fcp: -49%
• ↑ loadNewAccount/lcp: +1075%
• ↓ confirmTx/longTaskCount: -100%
• ↓ confirmTx/longTaskTotalDuration: -100%
• ↓ confirmTx/longTaskMaxDuration: -100%
• ↓ confirmTx/tbt: -100%
• ↓ confirmTx/fcp: -53%
• ↑ confirmTx/lcp: +1093%
• ↑ bridgeUserActions/bridge_load_page: +66%
• ↑ bridgeUserActions/bridge_load_asset_picker: +56%
• ↓ bridgeUserActions/longTaskCount: -100%
• ↓ bridgeUserActions/longTaskTotalDuration: -100%
• ↓ bridgeUserActions/longTaskMaxDuration: -100%
• ↓ bridgeUserActions/tbt: -100%
• ↑ bridgeUserActions/total: +16%
• ↓ bridgeUserActions/inp: -32%
• ↑ bridgeUserActions/lcp: +1112%

Startup Benchmarks · Samples: 100

Benchmark	chrome-webpack	firefox-webpack
startupStandardHome [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log] 🟡 loadScripts
startupPowerUserHome [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]

📈 Results compared to the previous 5 runs on main

• ↓ startupStandardHome/uiStartup: -18%
• ↓ startupStandardHome/load: -19%
• ↓ startupStandardHome/domContentLoaded: -19%
• ↓ startupStandardHome/domInteractive: -16%
• ↓ startupStandardHome/backgroundConnect: -18%
• ↓ startupStandardHome/firstReactRender: -15%
• ↓ startupStandardHome/loadScripts: -19%
• ↓ startupStandardHome/setupStore: -18%
• ↓ startupStandardHome/longTaskTotalDuration: -21%
• ↓ startupStandardHome/longTaskMaxDuration: -22%
• ↓ startupStandardHome/tbt: -26%
• ↓ startupStandardHome/inp: -11%
• ↓ startupStandardHome/fcp: -19%
• ↓ startupStandardHome/lcp: -15%
• ↑ startupPowerUserHome/setupStore: +10%
• ↓ startupPowerUserHome/numNetworkReqs: -31%
• ↑ startupPowerUserHome/longTaskTotalDuration: +10%
• ↑ startupPowerUserHome/tbt: +10%
• ↑ startupPowerUserHome/inp: +14%
• ↑ startupStandardHome/uiStartup: +13%
• ↑ startupStandardHome/load: +10%
• ↑ startupStandardHome/domContentLoaded: +10%
• ↑ startupStandardHome/domInteractive: +16%
• ↑ startupStandardHome/backgroundConnect: +31%
• ↑ startupStandardHome/firstReactRender: +25%
• ↑ startupStandardHome/setupStore: +52%
• ↑ startupStandardHome/inp: +100%
• ↑ startupStandardHome/fcp: +18%
• ↑ startupStandardHome/lcp: +14%
• ↓ startupPowerUserHome/domInteractive: -14%
• ↓ startupPowerUserHome/numNetworkReqs: -11%
• ↓ startupPowerUserHome/fcp: -14%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🔴 startupPowerUserHome/INP: p75 560ms
• 🟡 startupPowerUserHome/LCP: p75 2.8s

User Journey Benchmarks · Samples: 5 · real API 🔴 3

Benchmark	chrome-webpack	firefox-webpack
onboardingImportWallet [Sentry log · main/release]	🔴 [CI log] 🔴 doneButtonToHomeScreen 🔴 total	🔴 [CI log] 🟡 doneButtonToHomeScreen 🔴 total
onboardingNewWallet [Sentry log · main/release]	🟢 [CI log]	🔴 [CI log] 🔴 total
assetDetails [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
solanaAssetDetails [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]
importSrpHome [Sentry log · main/release]	🟡 [CI log]	🟢 [CI log]
sendTransactions [Sentry log · main/release]	🟡 [CI log]	🟢 [CI log]
swap [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]

📈 Results compared to the previous 5 runs on main

• ↓ onboardingImportWallet/doneButtonToHomeScreen: -18%
• ↓ onboardingImportWallet/openAccountMenuToAccountListLoaded: -15%
• ↑ onboardingImportWallet/longTaskTotalDuration: +19%
• ↑ onboardingImportWallet/longTaskMaxDuration: +13%
• ↑ onboardingImportWallet/tbt: +25%
• ↓ onboardingImportWallet/total: -11%
• ↓ onboardingNewWallet/tbt: -21%
• ↑ solanaAssetDetails/assetClickToPriceChart: +31%
• ↑ solanaAssetDetails/longTaskCount: +400%
• ↑ solanaAssetDetails/longTaskTotalDuration: +359%
• ↑ solanaAssetDetails/longTaskMaxDuration: +359%
• ↑ solanaAssetDetails/tbt: +317%
• ↑ solanaAssetDetails/total: +31%
• ↑ solanaAssetDetails/inp: +11%
• ↑ solanaAssetDetails/cls: +59%
• ↓ importSrpHome/loginToHomeScreen: -12%
• ↑ importSrpHome/longTaskCount: +21%
• ↓ sendTransactions/openSendPageFromHome: -15%
• ↑ sendTransactions/tbt: +14%
• ↓ sendTransactions/inp: -10%
• ↑ sendTransactions/lcp: +11%
• ↑ sendTransactions/cls: +59%
• ↑ swap/openSwapPageFromHome: +16%
• ↑ swap/fetchAndDisplaySwapQuotes: +12%
• ↑ swap/longTaskCount: +67%
• ↑ swap/longTaskTotalDuration: +48%
• ↑ swap/longTaskMaxDuration: +78%
• ↑ swap/tbt: +26%
• ↑ swap/total: +12%
• ↑ swap/inp: +13%
• ↓ swap/lcp: -64%
• ↓ swap/cls: -39%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🟡 importSrpHome/INP: p75 240ms
• 🟡 sendTransactions/INP: p75 216ms
• 🟡 solanaAssetDetails/FCP: p75 1.9s
• 🟡 swap/FCP: p75 1.9s

Dapp Page Load Benchmarks · Samples: 100

Benchmark	chrome-webpack
dappPageLoad [Sentry log · main/release]	🟢 [CI log]

Bundle size diffs

• background: 113 Bytes (0%)
• ui: 10 Bytes (0%)
• common: 300 Bytes (0%)

AI Test Plan

Risk Score	High Risk	Medium Risk	Files Changed	Commits
57/100	7	4	1587	111

Cherry-Pick Scenarios (1)

High Risk Scenarios (1)

1. Token Management – Import/display tokens without symbols

Risk Level: HIGH

Why This Matters: Cherry-pick #43515 fixes crashes when a token lacks a symbol; regressions could break the assets view and core send/receive flows.

Test Steps:

1. On Mainnet, import a custom token that has an empty or missing symbol (manually input contract); confirm it adds successfully.
2. Verify the asset list renders the token with a safe placeholder (e.g., contract address or generic label) without crashing.
3. Attempt to send the token and confirm the send form, confirmation, and activity list all render without relying on the symbol.
4. Remove and re-add the same token and confirm consistent behavior and no UI exceptions.

---

Release Scenarios (10)

High Risk Scenarios (6)

1. State Migrations (212/213) – Existing users with complex asset sets

Risk Level: HIGH

Why This Matters: New migrations can corrupt or drop asset/network state, causing missing assets, duplicates, or broken balances after upgrade.

Test Steps:

1. Start with a 13.35 profile containing: Mainnet + at least one custom network (e.g., Polygon), 6+ custom ERC-20 tokens (some hidden), and 3+ NFTs.
2. Upgrade to 13.36, open the extension, and wait for the home screen to fully load.
3. Verify no duplicate tokens appear, previously hidden tokens remain hidden, and NFT collections/items are intact.
4. Switch to the custom network and confirm custom RPC, watch tokens, and hidden/visible status are preserved per-network.
5. Refresh the extension and confirm balances/fiat values update and persist correctly.

---

2. Assets Controller upgrade – Token detection/import and per-network integrity

Risk Level: HIGH

Why This Matters: Assets Controller changes can break token management across networks, causing duplicates, incorrect labels, or missing balances.

Test Steps:

1. On Mainnet, import multiple custom tokens with varied metadata (0 decimals, 18 decimals, very long symbol/name) and enable/disable token detection.
2. Switch between Mainnet and another network (e.g., Arbitrum) and import a token with the same contract on both networks.
3. Verify no cross-network bleed (tokens only appear on the network where added) and no unintended symbol/name overrides from detection.
4. Remove and re-add a previously imported token and confirm historical activity remains intact and no duplicates appear.
5. Confirm balances and fiat values update after a minute or after triggering a manual refresh.

---

3. Transaction Send Flow – Gas estimation and fee editing (Transaction Pay Controller patch)

Risk Level: HIGH

Why This Matters: Small controller changes around fees can break send confirmations, misprice gas, or cause failed/broadcast-stuck transactions.

Test Steps:

1. On Mainnet, send ETH to a new address; verify EIP-1559 estimates (Low/Market/Aggressive) populate correctly.
2. Open Advanced gas settings, manually adjust max priority/fee and ensure the total updates correctly and confirmation is enabled.
3. Repeat on an L2 (e.g., Optimism) and verify fee display units, confirmation, and final posted gas values in the activity detail.
4. Attempt a low-gas scenario (set fees below suggested) and confirm validation prevents or warns appropriately.
5. Complete the transactions and verify status and fees reported in activity match expectations.

---

4. Activity List Avatars – Swaps, approvals, contract interactions

Risk Level: HIGH

Why This Matters: The avatar component change can produce broken/bad icons or crashes in the high-traffic activity view.

Test Steps:

1. Perform a token approval then a token transfer; check the activity list shows correct avatars/icons for each item.
2. Execute a swap via the built-in Swaps; verify avatar shows swap-appropriate icon and counterparty visuals.
3. Perform a generic contract interaction from a dapp; confirm fallback icon/identicon renders if no icon is available.
4. Open each activity detail panel to ensure no broken images or layout jumps occur.
5. Scroll through a long activity history and confirm avatars load progressively without flicker or errors.

---

5. NFT Activity and Avatar Fallbacks

Risk Level: HIGH

Why This Matters: UI fallback paths for NFTs are prone to null/404 cases; regressions here can break activity rendering or mislead users.

Test Steps:

1. Receive an NFT, then transfer it; verify the activity list uses the NFT image when available.
2. For an NFT with a broken/404 image, confirm the avatar falls back to a placeholder/identicon without errors.
3. Open NFT details from the asset tab and the activity item to validate consistent imagery and titles.
4. Switch networks and confirm NFT avatars are scoped correctly per network (no cross-network images/data).

---

6. Network switching while transactions are pending

Risk Level: HIGH

Why This Matters: Controller/UI synchronization during network changes can orphan pending activity or confuse users about the state of their transactions.

Test Steps:

1. Start a pending transaction on Mainnet (simulate slow gas or use low gas).
2. Switch to another network (e.g., Base) while the transaction is pending.
3. Verify any alert/interstitial appears correctly, allows safe cancel/dismiss, and the switch succeeds or is blocked as expected.
4. Return to Mainnet and ensure the pending transaction is still visible with correct status.
5. Complete or speed up the transaction and confirm final state is consistent in activity.

---

Medium Risk Scenarios (4)

1. MetaMetrics – Onboarding opt-in/out and settings toggle

Risk Level: MEDIUM

Why This Matters: New platform adapter code can break opt-in/out flows or the persistence of telemetry preferences.

Test Steps:

1. Start a fresh profile and go through onboarding; choose to decline metrics.
2. Confirm you reach the home screen without further prompts and the Metrics toggle is Off in Settings.
3. Toggle MetaMetrics On in Settings and confirm the confirmation dialog flows correctly and state persists after reload.
4. Toggle back Off and confirm prompt/confirmation behavior and persistence.

---

2. Alert Modal – Destructive and interstitial actions

Risk Level: MEDIUM

Why This Matters: Alert modal changes can cause users to inadvertently perform or fail to perform critical actions, impacting safety and trust.

Test Steps:

1. Trigger a known alert (e.g., Reset Account or Disconnect Site) and confirm modal copy, primary/secondary actions, and keyboard ESC/Enter behavior.
2. Confirm clicking backdrop behaves as specified (closes or blocks) and focus is trapped within the modal for accessibility.
3. Validate that choosing Cancel or X closes without side-effects, and Confirm applies the action and updates UI state immediately.

---

3. Account List Selection – Send screen and account switcher

Risk Level: MEDIUM

Why This Matters: Small list rendering changes can cause selection bugs or misrouting of funds from the wrong account.

Test Steps:

1. Add 8+ accounts (including a hardware account if available) and open the account switcher.
2. Select different accounts rapidly and confirm the selected account updates in the header and home balance.
3. Open the Send screen and switch accounts mid-flow; verify the form resets/retains values appropriately and no stale account state remains.
4. Validate long names/emojis do not clip or overlap in the list.

---

4. Assets Migration UI gating (selectors/assets-migration)

Risk Level: MEDIUM

Why This Matters: Selector logic changes can cause incorrect or persistent migration prompts, confusing users post-upgrade.

Test Steps:

1. Upgrade an existing profile and observe whether any migration banners/prompts appear on home or assets screens.
2. Confirm banners appear only when criteria are met (e.g., legacy state needing conversion) and do not show for fresh installs.
3. Dismiss the banner and verify it does not reappear unnecessarily after reload or network switch.

---

Teams Sign-off Status

Signed off: None yet

Awaiting sign-off (7):
Accounts, Assets, Networks, Onboarding, Settings, Swaps, Transactions

---

Generated by AI Test Plan Analyzer (gpt-5) at 2026-06-13T06:28:46.011Z

AI generated test plan (JSON): test-plan-13.36.0.json

[metamaskbotv2]

Builds ready [3d08648]

• ⚠️ Make sure the build is safe before downloading and running this build.
  • Please do not use these builds with accounts that contain significant real money.
  • Beware the security risks of cache poisoning.
• Webpack builds: chrome, firefox
• Webpack builds (beta): chrome, firefox
• Webpack builds (flask): chrome, firefox
• Webpack builds (test): chrome, firefox
• Webpack builds (test-flask): chrome, firefox
• bundle size: Bundle Size Stats
• bundle analyzer: Bundle Analyzer
• interaction-benchmark: Interaction Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts

Deprecated Browserify fallback builds

• Browserify builds: chrome, firefox
• Browserify builds (beta): chrome, firefox
• Browserify builds (flask): chrome, firefox
• Browserify builds (test): chrome, firefox
• Browserify builds (test-flask): chrome, firefox

⚡ Performance Benchmarks (Total: 🟢 14 pass · 🟡 8 warn · 🔴 3 fail)

Baseline (latest main): 5682526 | Date: 6/13/2026 | Pipeline: 27488342067 | Baseline logs

Metrics	chrome-webpack	firefox-webpack
onboardingImportWallet [Sentry log · main/release]	🔴 pwFormToMetricsScreen(p95) [CI log]	🔴 [CI log]
onboardingNewWallet [Sentry log · main/release]	🟢 [CI log]	🔴 [CI log]

Regressions (🔴 3 failures)

• onboardingImportWallet [Sentry log · main/release] · chrome-webpack — total(p75) [CI log]
• onboardingImportWallet [Sentry log · main/release] · firefox-webpack — total(p75) [CI log]
• onboardingNewWallet [Sentry log · main/release] · firefox-webpack — total(p75) [CI log]

Interaction Benchmarks · Samples: 5

Benchmark	chrome-webpack	firefox-webpack
loadNewAccount [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]
confirmTx [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]
bridgeUserActions [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]

📈 Results compared to the previous 5 runs on main

• ↑ loadNewAccount/load_new_account: +65%
• ↑ loadNewAccount/total: +65%
• ↑ loadNewAccount/inp: +37%
• ↑ confirmTx/tbt: +10%
• ↑ confirmTx/inp: +40%
• ↓ bridgeUserActions/bridge_load_page: -24%
• ↑ bridgeUserActions/bridge_load_asset_picker: +11%
• ↓ bridgeUserActions/tbt: -21%
• ↑ bridgeUserActions/inp: +29%
• ↑ loadNewAccount/load_new_account: +100%
• ↑ loadNewAccount/total: +100%
• ↑ loadNewAccount/inp: +37%
• ↑ loadNewAccount/fcp: +16%
• ↑ loadNewAccount/lcp: +1186%
• ↑ confirmTx/confirm_tx: +11%
• ↓ confirmTx/longTaskCount: -100%
• ↓ confirmTx/longTaskTotalDuration: -100%
• ↓ confirmTx/longTaskMaxDuration: -100%
• ↓ confirmTx/tbt: -100%
• ↑ confirmTx/total: +11%
• ↑ confirmTx/inp: +30%
• ↑ confirmTx/fcp: +20%
• ↑ confirmTx/lcp: +1212%
• ↑ bridgeUserActions/bridge_load_page: +107%
• ↑ bridgeUserActions/bridge_load_asset_picker: +90%
• ↓ bridgeUserActions/longTaskCount: -100%
• ↓ bridgeUserActions/longTaskTotalDuration: -100%
• ↓ bridgeUserActions/longTaskMaxDuration: -100%
• ↓ bridgeUserActions/tbt: -100%
• ↑ bridgeUserActions/total: +20%
• ↑ bridgeUserActions/inp: +36%
• ↑ bridgeUserActions/lcp: +1139%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🟡 loadNewAccount/FCP: p75 2.0s
• 🟡 confirmTx/FCP: p75 2.0s

Startup Benchmarks · Samples: 100

Benchmark	chrome-webpack	firefox-webpack
startupStandardHome [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
startupPowerUserHome [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]

📈 Results compared to the previous 5 runs on main

• ↓ startupStandardHome/firstPaint: -12%
• ↓ startupStandardHome/lcp: -12%
• ↑ startupPowerUserHome/domInteractive: +17%
• ↓ startupPowerUserHome/numNetworkReqs: -31%
• ↑ startupPowerUserHome/tbt: +11%
• ↑ startupPowerUserHome/inp: +12%
• ↑ startupStandardHome/domInteractive: +19%
• ↑ startupStandardHome/inp: +50%
• ↑ startupStandardHome/fcp: +18%
• ↓ startupPowerUserHome/backgroundConnect: -16%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🔴 startupPowerUserHome/INP: p75 552ms
• 🟡 startupPowerUserHome/LCP: p75 3.1s

User Journey Benchmarks · Samples: 5 · real API 🔴 3

Benchmark	chrome-webpack	firefox-webpack
onboardingImportWallet [Sentry log · main/release]	🔴 [CI log] 🔴 doneButtonToHomeScreen 🔴 total	🔴 [CI log] 🔴 total
onboardingNewWallet [Sentry log · main/release]	🟢 [CI log]	🔴 [CI log] 🔴 total
assetDetails [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
solanaAssetDetails [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]
importSrpHome [Sentry log · main/release]	🟢 [CI log]	🟢 [CI log]
sendTransactions [Sentry log · main/release]	🟡 [CI log]	🟡 [CI log]
swap [Sentry log · main/release]	🟢 [CI log]	🟡 [CI log]

📈 Results compared to the previous 5 runs on main

• ↓ onboardingImportWallet/doneButtonToHomeScreen: -16%
• ↑ onboardingImportWallet/openAccountMenuToAccountListLoaded: +23%
• ↑ onboardingImportWallet/longTaskMaxDuration: +12%
• ↑ onboardingImportWallet/tbt: +15%
• ↓ onboardingNewWallet/agreeButtonToOnboardingSuccess: -24%
• ↓ onboardingNewWallet/longTaskTotalDuration: -13%
• ↓ onboardingNewWallet/tbt: -32%
• ↑ solanaAssetDetails/assetClickToPriceChart: +28%
• ↓ solanaAssetDetails/longTaskCount: -100%
• ↓ solanaAssetDetails/longTaskTotalDuration: -100%
• ↓ solanaAssetDetails/longTaskMaxDuration: -100%
• ↓ solanaAssetDetails/tbt: -100%
• ↑ solanaAssetDetails/total: +28%
• ↑ solanaAssetDetails/cls: +59%
• ↓ importSrpHome/loginToHomeScreen: -28%
• ↓ importSrpHome/openAccountMenuAfterLogin: -27%
• ↓ importSrpHome/homeAfterImportWithNewWallet: -22%
• ↓ importSrpHome/longTaskCount: -14%
• ↓ importSrpHome/longTaskTotalDuration: -30%
• ↓ importSrpHome/longTaskMaxDuration: -25%
• ↓ importSrpHome/tbt: -53%
• ↓ importSrpHome/total: -23%
• ↓ importSrpHome/inp: -35%
• ↓ importSrpHome/fcp: -26%
• ↓ importSrpHome/lcp: -18%
• ↓ sendTransactions/openSendPageFromHome: -12%
• ↑ sendTransactions/selectTokenToSendFormLoaded: +46%
• ↓ sendTransactions/reviewTransactionToConfirmationPage: -53%
• ↓ sendTransactions/longTaskTotalDuration: -11%
• ↓ sendTransactions/tbt: -36%
• ↓ sendTransactions/total: -51%
• ↓ sendTransactions/inp: -13%
• ↓ sendTransactions/cls: -67%
• ↑ swap/openSwapPageFromHome: +31%
• ↑ swap/fetchAndDisplaySwapQuotes: +40%
• ↑ swap/longTaskCount: +67%
• ↑ swap/longTaskTotalDuration: +75%
• ↑ swap/longTaskMaxDuration: +70%
• ↑ swap/tbt: +84%
• ↑ swap/total: +40%
• ↓ swap/lcp: -59%
• ↓ swap/cls: -39%

🌐 Core Web Vitals — 🟢 good · 🟡 needs improvement · 🔴 poor (web.dev thresholds)

• 🟡 sendTransactions/INP: p75 208ms
• 🟡 solanaAssetDetails/FCP: p75 2.0s
• 🟡 sendTransactions/FCP: p75 1.9s
• 🟡 swap/FCP: p75 1.9s

Dapp Page Load Benchmarks · Samples: 100

Benchmark	chrome-webpack
dappPageLoad [Sentry log · main/release]	🟢 [CI log]

Bundle size diffs

• background: 113 Bytes (0%)
• ui: 10 Bytes (0%)
• common: 326 Bytes (0%)

AI Test Plan

Risk Score	High Risk	Medium Risk	Files Changed	Commits
51/100	5	6	1587	112

Cherry-Pick Scenarios (1)

Medium Risk Scenarios (1)

1. Token Management – handling tokens with missing symbol

Risk Level: MEDIUM

Why This Matters: Cherry-pick 43515 fixes a crash where tokens without a symbol could break the app; regression would cause app instability on portfolios holding such tokens.

Test Steps:

1. On a test network, add or detect an ERC-20 whose contract returns an empty or null symbol (or uses a known test token without a symbol).
2. Open the Assets and Activity tabs; verify the app does not crash and the token row shows a safe fallback label (e.g., contract address/placeholder).
3. Initiate a send of the symbol-less token and confirm the confirmation screen and activity item render without errors.
4. Hide/unhide the token and refresh; verify stable behavior and no re-render loops.

---

Release Scenarios (10)

High Risk Scenarios (5)

1. State Migrations (212 & 213) – persisted wallet data

Risk Level: HIGH

Why This Matters: Migrations change stored data formats; any error can cause data loss, missing tokens/NFTs, or inability to load the wallet.

Test Steps:

1. Start on 13.35.x with at least 2 accounts, tokens on Mainnet and a testnet (e.g., Goerli/Seploia), and at least one NFT; close the extension.
2. Update to 13.36.0 and open the extension; wait for the home screen to load (let background complete migrations).
3. Verify all accounts, tokens (including custom/hidden), NFTs, and connected sites persist; balances and fiat values load without errors.
4. Switch networks (Mainnet -> testnet -> custom RPC) and confirm token/NFT lists and activity remain intact on each network.

---

2. State Migrations – locked state and edge data

Risk Level: HIGH

Why This Matters: Users often update while locked; migration must safely resume post-unlock and handle edge records without bricking the UI.

Test Steps:

1. On 13.35.x, lock the wallet with tokens/NFTs configured (including at least one custom token), then update to 13.36.0.
2. Open the extension while locked; unlock and observe initial load.
3. Confirm the app does not hang or show blank/loader screens; token lists render, activity populates, and no 'failed to migrate' or 'cannot load tokens' errors appear.
4. Verify advanced settings > state log (if available) shows latest migration version applied and there are no repeating migration retries.

---

3. Token Management – Assets Controller update (autodetection, metadata, pricing)

Risk Level: HIGH

Why This Matters: Assets controller powers token lists and metadata; regressions can cause wrong balances, duplicates, or UI crashes.

Test Steps:

1. Enable token detection on Mainnet and one testnet; ensure multiple tokens (with/without logos) appear with balances and fiat values where applicable.
2. Add a custom ERC-20 on Mainnet and the same address on a testnet; confirm tokens are correctly scoped to each network (no cross-network duplication).
3. Hide a detected token, then refresh and switch networks; verify it stays hidden on that specific network and is not immediately re-added.
4. Confirm tokens with missing metadata (logo/name) render safe fallbacks and do not break portfolio or activity views.

---

4. Transaction Flow – Transaction Pay Controller (gas estimation, EIP-1559 vs legacy)

Risk Level: HIGH

Why This Matters: Incorrect gas suggestions or replacement logic can cause failed or stuck transactions, directly impacting core wallet functionality.

Test Steps:

1. On an EIP-1559 network (e.g., Mainnet), send native ETH; verify suggested maxFee and maxPriorityFee show and can be edited, then confirm.
2. Speed up the pending transaction and then attempt to cancel it; verify correct replacement transactions are created and status updates correctly.
3. On a legacy gas network (e.g., BSC or a legacy custom RPC), send the native token and confirm gas price fields (no EIP-1559) are shown and the transaction completes.

---

5. Privacy & Analytics – New analytics platform adapter and method/action mapping

Risk Level: HIGH

Why This Matters: Analytics transport changes can violate privacy expectations or block critical user actions if events cause errors.

Test Steps:

1. Fresh install: decline metrics; connect to a test dapp, open/close popups, and send a small test transaction.
2. In the background DevTools Network panel, verify no analytics/metrics requests are sent while opted out.
3. Enable metrics in Settings > Security & Privacy; repeat key actions (connect, send); verify analytics requests now appear and do not include sensitive payloads (addresses/amounts redacted as per policy).

---

Medium Risk Scenarios (5)

1. Global Alerts & Modals – alert system changes (blocking errors and warnings)

Risk Level: MEDIUM

Why This Matters: Global alerts block critical flows; regressions can trap users in modals or silently fail transactions.

Test Steps:

1. Trigger an error alert by attempting to send more than the available balance; verify the alert modal renders fully and can be dismissed.
2. Trigger a security/warning alert (e.g., connect to an unverified site or simulate a bad network switch) and confirm actions in the modal work and return you to a stable state.
3. Ensure focus is trapped in the modal and keyboard navigation allows dismiss/confirm without freezing the UI.

---

2. Activity Feed – avatars/icons for tokens and NFTs

Risk Level: MEDIUM

Why This Matters: Recent UI changes to avatars can cause broken images or crashes in the most-visited screen (activity).

Test Steps:

1. Perform a native send, an ERC-20 send, and an NFT (ERC-721 or ERC-1155) transfer; open Activity.
2. Verify each activity item shows the correct avatar/icon or a safe fallback without broken images.
3. Open the activity details view for each and confirm icons, titles, and amounts are consistent.

---

3. Account Switching – account list item rendering and selection

Risk Level: MEDIUM

Why This Matters: Small UI changes to account list can break selection, labeling, or lead to user confusion when switching send-from accounts.

Test Steps:

1. Create/import 6–10 accounts and connect at least one hardware account; open the account switcher.
2. Scroll and select different accounts; verify the selected account address and balance update immediately on home.
3. Rename an account and confirm the updated label appears correctly in the list and activity.

---

4. Portfolio/Token Totals – cross-network asset aggregation and selectors

Risk Level: MEDIUM

Why This Matters: Selector logic changes can miscompute totals, leading to incorrect balances and user trust issues.

Test Steps:

1. With balances on Mainnet and a testnet, open Portfolio/Assets; confirm fiat totals and per-network subtotals are accurate.
2. Hide one token and verify totals update immediately and remain correct after a refresh and network switch.
3. Switch to an account with no assets; confirm totals drop to zero and no stale values remain.

---

5. NFTs – detection and display (metadata fallbacks)

Risk Level: MEDIUM

Why This Matters: Assets controller and UI updates can break NFT rendering or transfers, a common support pain point.

Test Steps:

1. Add at least one ERC-721 and one ERC-1155 NFT across two networks; open the NFTs tab.
2. Verify images and names appear, or safe fallbacks are shown; no blank cards or crashes.
3. Transfer an NFT and confirm the NFTs tab and Activity update consistently with the correct icon.

---

Teams Sign-off Status

Signed off: None yet

Awaiting sign-off (6):
Accounts, Assets, Networks, Security, Transactions, Wallet

---

Generated by AI Test Plan Analyzer (gpt-5) at 2026-06-14T05:00:09.060Z

AI generated test plan (JSON): test-plan-13.36.0.json