[Snyk] Security upgrade @ledgerhq/hw-app-eth from 6.24.1 to 6.38.1

[kingjay66]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Input Validation 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)
🦉 Improper Input Validation

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@ledgerhq/hw-app-eth@6.38.1	Transitive: environment, filesystem, network	+49	81 MB	aboissiere, gbrahm-ledger, ldg-github-ci, ...5 more
npm/bignumber.js@9.1.2	None	0	351 kB	mikemcl

🚮 Removed packages: npm/@ledgerhq/hw-app-eth@6.24.1, npm/bignumber.js@9.1.0, npm/enhanced-resolve@5.8.3, npm/enzyme-adapter-react-16@1.15.7, npm/enzyme@3.11.0, npm/eslint-config-prettier@8.6.0, npm/eslint-config-standard-with-typescript@34.0.0, npm/eslint@8.33.0

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
Network access	npm/form-data@4.0.0	Module: http Location: Package overview	package-lock.json package.json	🚫
Network access	npm/form-data@4.0.0	Module: https Location: Package overview	package-lock.json package.json	🚫
Filesystem access	npm/form-data@4.0.0	Module: fs Location: Package overview	package-lock.json package.json	🚫
New author	npm/bech32@1.1.4	New Author: junderw Previous Author: dcousens	Source	🚫
Network access	npm/@ethersproject/providers@5.7.2	Module: net Location: Package overview	Source	🚫
Environment variable access	npm/scheduler@0.23.2	Env Vars: NODE_ENV Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/react-dom@18.3.1	Env Vars: NODE_ENV Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/react@18.3.1	Env Vars: NODE_ENV Location: Package overview	package-lock.json package.json	🚫
Network access	npm/axios@1.7.3	Module: globalThis["fetch"] Location: Package overview	package-lock.json package.json	🚫
Network access	npm/follow-redirects@1.15.9	Module: http Location: Package overview	package-lock.json package.json	🚫
Network access	npm/follow-redirects@1.15.9	Module: https Location: Package overview	package-lock.json package.json	🚫

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

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/form-data@4.0.0
• @SocketSecurity ignore npm/bech32@1.1.4
• @SocketSecurity ignore npm/@ethersproject/providers@5.7.2
• @SocketSecurity ignore npm/scheduler@0.23.2
• @SocketSecurity ignore npm/react-dom@18.3.1
• @SocketSecurity ignore npm/react@18.3.1
• @SocketSecurity ignore npm/axios@1.7.3
• @SocketSecurity ignore npm/follow-redirects@1.15.9