[Snyk] Security upgrade @mempool/mempool.js from 2.3.0 to 3.0.0

[Brandylee24]

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

Snyk changed the following file(s):

• frontend/package.json
• frontend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Denial of Service (DoS) SNYK-JS-WS-7266574	696
	Improper Handling of Extra Parameters SNYK-JS-FOLLOWREDIRECTS-6141137	686
	Cross-site Request Forgery (CSRF) SNYK-JS-AXIOS-6032459	676
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-6444610	646
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AXIOS-6124857	586

---

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:

🦉 Cross-site Request Forgery (CSRF)
🦉 Regular Expression Denial of Service (ReDoS)

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@babel/[email protected]	environment, filesystem, unsafe Transitive: shell	+44	10.5 MB	nicolo-ribaudo
npm/@mempool/[email protected]	network	0	19.4 kB	softsimon
npm/@types/[email protected]	None	0	11.4 kB	types
npm/@types/[email protected]	None	0	59.9 kB	types
npm/@types/[email protected]	None	+7	90 kB	types
npm/@types/[email protected]	Transitive: environment, filesystem, unsafe	+37	1.41 MB	types
npm/@types/[email protected]	None	0	1.67 MB	types
npm/@types/[email protected]	None	0	3.43 MB	types
npm/@types/[email protected]	None	0	21.5 kB	types
npm/@typescript-eslint/[email protected]	Transitive: environment, filesystem	+8	3.99 MB	jameshenry
npm/@typescript-eslint/[email protected]	Transitive: environment, filesystem	+5	1.31 MB	jameshenry
npm/[email protected]	environment, network Transitive: filesystem	+7	788 kB	jasonsaayman
npm/[email protected]	Transitive: environment	+19	635 kB	junderw
npm/[email protected]	None	0	444 kB	evanvosberg
npm/[email protected]	None	0	18.2 kB	lydell
npm/[email protected]	filesystem Transitive: environment, unsafe	+10	4.16 MB	eslintbot
npm/[email protected]	environment, filesystem, network Transitive: eval	+3	527 kB	dougwilson
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+243	14.1 MB	simenb
npm/[email protected]	filesystem, network	+2	85 kB	runk
npm/[email protected]	environment, network Transitive: eval	+14	1.19 MB	sidorares
npm/[email protected]	None	0	39.3 kB	mokuo
npm/[email protected]	environment, filesystem, unsafe	0	15.8 MB	prettier-bot
npm/[email protected]	environment, filesystem, unsafe	0	11.7 MB	prettier-bot
npm/[email protected]	None	0	120 kB	thomasdondorf
npm/[email protected]	environment, eval, filesystem, network, shell	+32	7.23 MB	google-wombot
npm/[email protected]	network Transitive: environment	+5	425 kB	kikobeats
npm/[email protected]	environment, filesystem, unsafe Transitive: eval, network, shell	+114	8.46 MB	kul
npm/[email protected]	environment, filesystem, unsafe	+16	1.95 MB	cspotcode
npm/[email protected]	None	0	67.2 MB	typescript-bot
npm/[email protected]	environment, network	0	135 kB	lpinca

🚮 Removed packages: npm/@fortawesome/[email protected], npm/@fortawesome/[email protected], npm/@fortawesome/[email protected], npm/@fortawesome/[email protected], npm/@mempool/[email protected], npm/@ng-bootstrap/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

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
Critical CVE	npm/[email protected]	CVE: GHSA-xwcq-pm8m-c4vf crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard (CRITICAL) Affected versions: < 4.2.0 Patched version: 4.2.0	backend/package-lock.json backend/package.json	⚠︎
Critical CVE	npm/[email protected]	CVE: GHSA-fpw7-j2hg-69v5 mysql2 Remote Code Execution (RCE) via the readCodeFor function (CRITICAL) Affected versions: < 3.9.4 Patched version: 3.9.4	backend/package-lock.json backend/package.json	⚠︎
Critical CVE	npm/[email protected]	CVE: GHSA-4rch-2fh8-94vw MySQL2 for Node Arbitrary Code Injection (CRITICAL) Affected versions: < 3.9.7 Patched version: 3.9.7	backend/package-lock.json backend/package.json	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

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

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]