[Snyk] Security upgrade @mux/mux-node from 7.3.5 to 8.0.0

[gabidobo]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• examples/with-mux-video/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-side Request Forgery (SSRF) SNYK-JS-AXIOS-7361793	833

---

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:

🦉 Server-side Request Forgery (SSRF)

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@apollo/client@3.11.4	network Transitive: environment, eval	+16	7.91 MB	apollo-bot
npm/@apollo/server@4.11.0	environment, network Transitive: eval, filesystem, unsafe	+79	8.9 MB	apollo-bot
npm/@as-integrations/next@1.3.0	Transitive: environment, filesystem, network, shell, unsafe	+14	1.11 GB	martinnabhan
npm/@faker-js/faker@7.6.0	None	0	9.35 MB	shinigami92
npm/@graphql-tools/schema@9.0.19	None	+4	698 kB	ardatan
npm/@hapi/iron@6.0.0	None	+5	120 kB	hueniverse
npm/@types/cors@2.8.17	None	0	5.91 kB	types
npm/@types/uuid@8.3.4	None	0	6.67 kB	types
npm/graphql-yoga@3.9.1	None	+12	9.91 MB	dotansimha
npm/graphql@16.6.0	environment	0	1.34 MB	i1g
npm/prop-types@15.8.1	environment	+3	139 kB	ljharb
npm/serve@13.0.4	Transitive: environment, eval, filesystem, network, shell	+68	4.02 MB	leerobinson
npm/uuid@8.1.0	None	0	95.2 kB	ctavan

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
Telemetry	npm/next@13.5.6	Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information	examples/api-routes-apollo-server-and-client-auth/package.json	🚫
Telemetry	npm/next@14.2.5	Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information	Source	🚫
AI detected potential malware	npm/next@14.2.5	Notes: The primary concern in the code is the use of vm.runInNewContext to execute file content, which can lead to arbitrary code execution if the file content is not trusted. This warrants a higher risk score. However, there is no evidence of malware or obfuscation in the code. Confidence: 0.60 Severity: 0.90	Source	🚫

View full report↗︎

Next steps

What is telemetry?

This package contains telemetry which tracks how it is used.

Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.

What is AI detected malware?

AI has identified this package as malware. This is a strong signal that the package may be malicious.

Given the AI system's identification of this package as malware, extreme caution is advised. It is recommended to avoid downloading or installing this package until the threat is confirmed or flagged as a false positive.

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/next@13.5.6
• @SocketSecurity ignore npm/next@14.2.5