[Snyk] Fix for 22 vulnerabilities

[Dargon789]

Snyk has created this PR to fix 22 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• apps/extension/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Information Exposure SNYK-JS-ELLIPTIC-8720086	251
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8187303	243
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577916	224
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577917	224
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-7577918	224
	Privilege Escalation SNYK-JS-OPENZEPPELINCONTRACTS-1570170	175
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	169
	Denial of Service (DoS) SNYK-JS-WS-7266574	169
	Denial of Service (DoS) SNYK-JS-JPEGJS-2859218	159
	Prototype Pollution SNYK-JS-UTILITIES-3184491	148
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	131
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8172694	130
	Deserialization of Untrusted Data SNYK-JS-OPENZEPPELINCONTRACTS-2320176	107
	Deserialization of Untrusted Data SNYK-JS-OPENZEPPELINCONTRACTS-6056529	107
	Improper Verification of Cryptographic Signature SNYK-JS-OPENZEPPELINCONTRACTS-2980279	102
	Cross-site Scripting SNYK-JS-SEND-7926862	79
	Cross-site Scripting SNYK-JS-SERVESTATIC-7926865	79
	Denial of Service (DoS) SNYK-JS-GRAPHQL-5905181	63
	Denial of Service (DoS) SNYK-JS-OPENZEPPELINCONTRACTS-2965798	45
	Improper Input Validation SNYK-JS-NANOID-8492085	44
	Denial of Service (DoS) SNYK-JS-OPENZEPPELINCONTRACTS-5425827	40
	Exposure of Sensitive Information to an Unauthorized Actor SNYK-JS-PHIN-6598077	39

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Improper Input Validation
🦉 Deserialization of Untrusted Data
🦉 More lessons are available in Snyk Learn

Summary by Sourcery

Bug Fixes:

• Updates yarn dependencies to address multiple vulnerabilities, including critical severity issues like Information Exposure and Improper Verification of Cryptographic Signature.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the ui, uniswap, and utilities dependencies in apps/extension/package.json to address 22 vulnerabilities identified by Snyk.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updates versions of ui, uniswap, and utilities dependencies to address multiple vulnerabilities.	Updated ui from workspace:^ to 0.0.0. Updated uniswap from workspace:^ to 0.0.1. Updated utilities from workspace:^ to 1.0.6.	apps/extension/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/utilities@1.0.6	filesystem, network	0	206 kB	mde

View full report↗︎

[socket-security]

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

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

Alert	Package	Note	Source	CI
High CVE	npm/utilities@1.0.6	CVE: GHSA-wxfj-84xf-7gxv mde utilities contains Prototype Pollution (HIGH) Affected versions: <= 1.0.6 Patched version: No patched versions	apps/mobile/package.json	⚠︎
Deprecated	npm/utilities@1.0.6	Reason: This package is no longer maintained and vulnerability exists.	apps/mobile/package.json	⚠︎

View full report↗︎

Next steps

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

Take a deeper look at the dependency

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

Remove the package

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

Mark a package as acceptable risk

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

• @SocketSecurity ignore npm/utilities@1.0.6