chore(deps): bump @metamask/profile-sync-controller from 16.0.0 to 25.1.1

[dependabot]

Bumps @metamask/profile-sync-controller from 16.0.0 to 25.1.1.

Commits

• 09f3fd5 Release/611.0.0 (#6810)
• 903c1a1 Release/610.0.0 (#6809)
• cc42c42 Release/609.0.0 (#6807)
• 34f185f feat: add blocklist paths flag for hotlist (#6808)
• 4483e68 Release/608.0.0 (#6806)
• 7878d3a change account type field name (#6804)
• 30107f4 chore: Add the optional "Client-Version" header in the Bridge Controller (#6791)
• f526ee0 feat: move and export notification isVersionInBounds util (#6793)
• 01b3e24 Release/607.0.0 (#6801)
• 8088f99 Release/606.0.0 (#6800)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Note

Bumps @metamask/profile-sync-controller to 25.1.1 and updates related MetaMask dependencies via lockfile refresh.

• Dependencies:
  • Upgrade @metamask/profile-sync-controller to ^25.1.1 in package.json.
  • Lockfile refresh updates numerous related @metamask/* packages (utils, controllers, keyring, snaps, providers) and prunes/replaces some older transitive deps.

^{Written by Cursor Bugbot for commit 9f122f0. This will update automatically on new commits. Configure here.}

[dependabot]

Assignees

The following users could not be added as assignees: protocol-galileo. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Please fix the above issues or remove invalid values from dependabot.yml.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
metamask-docs	Ready	Preview	Comment	Oct 23, 2025 2:12am

[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/​profile-sync-controller@​16.0.0 ⏵ 25.1.1	+2		+1	-2

View full report

[socket-security]

Warning

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)
Warn		@metamask/profile-sync-controller@25.1.1 is a AI-detected potential code anomaly. Notes: The code implements a guarded, cache-accelerated path to sign a message via an external SnapController. No explicit malware indicators detected. Primary risks relate to API design and cache semantics: entropySourceId is currently unused in the cache key, which could cause mismatches between the signing policy and cached signatures; potential replay/reuse concerns if identical messages are signed for different intents without provenance. Recommended improvements: validate message format and provenance, incorporate entropySourceId into cache keys or policy checks, add audit logging, and implement cache eviction/invalidation rules to prevent stale signatures. Confidence: 0.75 Severity: 0.55 From: package-lock.json → npm/@metamask/profile-sync-controller@25.1.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/profile-sync-controller@25.1.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.

View full report

[dependabot]

Superseded by #2412.