chore: upgrade ethereumjs packages

[matthewwalsh0]

Upgrade @ethereumjs/tx from ^4.2.0 to ^5.4.0.

Necessary to align with @metamask/transaction-controller which requires the latest version to support EIP-7702 transactions.

Note that the Keyring type is being deprecrated, but this update ensures alignment until the dependency is removed.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@ethereumjs/[email protected] 🔁 npm/@ethereumjs/[email protected]	None	0	713 kB	holgerd77
npm/@ethereumjs/[email protected] 🔁 npm/@ethereumjs/[email protected]	None	0	134 kB	holgerd77
npm/@ethereumjs/[email protected] 🔁 npm/@ethereumjs/[email protected]	None	0	785 kB	holgerd77
npm/@ethereumjs/[email protected] 🔁 npm/@ethereumjs/[email protected]	network	0	702 kB	holgerd77
npm/@noble/[email protected] 🔁 npm/@noble/[email protected]	None	0	1.5 MB	paulmillr
npm/@noble/[email protected] 🔁 npm/@noble/[email protected]	None	0	773 kB	paulmillr
npm/@scure/[email protected] 🔁 npm/@scure/[email protected]	None	0	133 kB	paulmillr
npm/@scure/[email protected] 🔁 npm/@scure/[email protected]	None	0	58.7 kB	paulmillr
npm/@scure/[email protected] 🔁 npm/@scure/[email protected]	None	0	374 kB	paulmillr
npm/[email protected] 🔁 npm/[email protected]	None	0	83.7 kB	paulmillr

🚮 Removed packages: npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@ethereumjs/[email protected], npm/@noble/[email protected], npm/@scure/[email protected], npm/@scure/[email protected], npm/@noble/[email protected], npm/[email protected], npm/@ethereumjs/[email protected], npm/@ethereumjs/[email protected], npm/@ethereumjs/[email protected], npm/@scure/[email protected]

View full report↗︎

Next steps

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

[matthewwalsh0]

@SocketSecurity ignore-all

It might be problematic to merge this PR since it's a breaking change.

[danroc]

@matthewwalsh0, I synced with @ccharly and probably this change should be made in the keyring-utils package and the transactions-controller should use the type from there instead.