[Snyk] Security upgrade @solana/spl-token from 0.2.0 to 0.3.2

[adamlaska]

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

Snyk changed the following file(s):

• web3.js/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8172694	701

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@blockworks-foundation/[email protected]	Transitive: environment, filesystem, network	+28	11.5 MB	riordanp
npm/@bonfida/[email protected]	Transitive: environment, filesystem, network	+31	124 MB	bonfida
npm/@bonfida/[email protected]	Transitive: environment, filesystem, network	+19	40.7 MB	bonfida
npm/@cloudflare/[email protected]	environment	0	118 kB	third774
npm/@metamask/[email protected]	None	+5	84.1 kB	whymarrh
npm/@metaplex/[email protected]	filesystem, network Transitive: environment	+18	5.89 MB	m-sebastiyan
npm/@popperjs/[email protected]	environment	0	1.59 MB	fezvrasta
npm/@project-serum/[email protected]	environment, filesystem, network	+5	2.41 MB	armaniferrante
npm/@project-serum/[email protected]	None	+7	6.03 MB	armaniferrante
npm/@react-hook/[email protected]	None	+1	50.6 kB	jaredlunde
npm/@sentry/[email protected]	Transitive: network	+5	1.82 MB	sentry-bot
npm/@solana/[email protected]	network	+1	12.5 MB	bartosz-lipinski
npm/@solana/[email protected]	network Transitive: environment, filesystem	+9	11.3 MB	_chido
npm/@testing-library/[email protected]	Transitive: filesystem	+6	607 kB	testing-library-bot
npm/@testing-library/[email protected]	environment	+24	7.98 MB	testing-library-bot
npm/@testing-library/[email protected]	Transitive: environment	+24	3.8 MB	testing-library-bot
npm/@types/[email protected]	None	0	45 kB	types
npm/@types/[email protected]	None	0	1.66 kB	types
npm/@types/[email protected]	Transitive: environment	+10	456 kB	types
npm/@types/[email protected]	None	0	1.7 MB	types
npm/@types/[email protected]	None	0	27.5 kB	types
npm/@types/[email protected]	None	+2	36.6 kB	types
npm/@types/[email protected]	None	+1	88.5 kB	types
npm/@types/[email protected]	None	+3	1.33 MB	types
npm/@types/[email protected]	None	0	1.7 kB	types
npm/[email protected]	None	0	8.65 MB	xhmikosr
npm/[email protected]	None	+4	1.51 MB	etimberg
npm/[email protected]	None	0	17.7 kB	dcousens
npm/[email protected]	network	0	98.7 kB	markmiscavage

🚮 Removed packages: npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@commitlint/[email protected], npm/@commitlint/[email protected], npm/@rollup/[email protected], npm/@rollup/[email protected], npm/@rollup/[email protected], npm/@rollup/[email protected], npm/@rollup/[email protected], npm/@rollup/[email protected], npm/@rollup/[email protected], npm/@solana/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@typescript-eslint/[email protected], npm/@typescript-eslint/[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], 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	CI
Critical CVE	npm/[email protected]	CVE: GHSA-phwq-j96m-2c2q ejs template injection vulnerability (CRITICAL) Affected versions: < 3.1.7 Patched version: 3.1.7	⚠︎
Protestware or potentially unwanted behavior	npm/[email protected]	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	⚠︎
Critical CVE	npm/[email protected]	CVE: GHSA-76p3-8jx3-jpfq Prototype pollution in webpack loader-utils (CRITICAL) Affected versions: < 1.4.1 Patched version: 1.4.1	⚠︎

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.

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package may come along with functionality unrelated to its primary purpose.

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]
• @SocketSecurity ignore npm/[email protected]