[Snyk] Upgrade tronweb from 4.4.0 to 5.3.2

[OKEAMAH]

Snyk has created this PR to upgrade tronweb from 4.4.0 to 5.3.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 7 versions ahead of your current version.

• The recommended version was released on 6 months ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Cross-site Request Forgery (CSRF) SNYK-JS-AXIOS-6032459	300	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AXIOS-6124857	300	Proof of Concept

Release notes

Package name: tronweb

• 5.3.2 - 2024-02-22
  
  • Add custom block header argument for building transactions locally in transactionBuilder lib
  • Support TIP586 by trx.getBandwidthPrices and trx.getEnergyPrices
  • Support recover transaction signer address by trx.ecRecover
  • Support multi-dimension address array such as address[][] for ABI params encoding in triggerSmartContract and createSmartContract #433
  • Fix error when triggerSmartContract with error address due to the undefined callback #429
  • Bump axios from 0.26.1 to 1.6.2 #445
• 5.3.1 - 2023-10-13
  
  • Fix getBlockRange() error for range of 1 (#398).
  • Add support for estimateenergy in TransactionBuilder#deployConstantContract() API.
• 5.3.0 - 2023-07-11
  
  • Replace elliptic with ethereum-cryptography/secp256k1
  • Bump ethers to ^6.6.0
  • Optimize argument validation for createToken, updateToken and applyForSR
  • callValue can be 0 when the contract constructor is payable
  • Support shouldPollResponse to customize poll times (#368)
  • Support TIP541 by transactionBuilder.cancelUnfreezeBalanceV2
  • Support TIP542 by adding a parameter in transactionBuilder.delegateResource
  • Support estimate the energy used in contract deployment by transactionBuilder.deployConstantContract
• 5.2.0 - 2023-05-17
  
  • Support build transactions locally with protobuf
  • Support multi-sign for setAccountId, updateBrokerage, clearABI, updateAccountPermissions function in transactionBuilder lib
• 5.1.1 - 2023-07-05
  
  • Support TIP541 and TIP542
• 5.1.0 - 2023-01-31
  
  • Add freezeBalanceV2, unfreezeBalanceV2, delegateResource, undelegateResource and withdrawExpireUnfreeze function in transactiobBuiler lib to support stakeV2
  • Support tronWeb.transactionBuilder.estimateEnergy to estimate energy for triggersmartcontract transaction
  • Add getDelegatedResourceV2, getDelegatedResourceAccountIndexV2, getCanDelegatedMaxSize, getAvailableUnfreezeCount and getCanWithdrawUnfreezeAmount function to query account resource info
• 5.0.0 - 2022-12-20
  
  • Add tronWeb.utils.transaction lib to serialize and deserialize transaction
  • Add tronWeb.utils.transaction.txJsonToPb function to convert transaction json to protobuf
  • Add tronWeb.utils.transaction.txPbToTxID function to get txID from transaction protobuf
  • Support new transaction builder createAccount
• 4.4.0 - 2022-09-28
  
  • Support createRandom and fromMnemonic function
  • Add tronWeb.utils.message lib, which includes hashMessage, signMessage and verifyMessage
  • Add signMessageV2 and verifyMessageV2 in tronWeb.trx lib which can support plain text signature and verification
  • Add size filter for event watch

from tronweb GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/dotenv@16.4.5	environment, filesystem	0	79.1 kB	motdotla
npm/eslint-config-prettier@9.1.0	None	0	20.8 kB	lydell
npm/eslint-plugin-prettier@5.1.3	None	+2	95.8 kB	jounqin
npm/eslint@8.57.0	environment, filesystem Transitive: eval, shell, unsafe	+86	10 MB	eslintbot
npm/fast-safe-stringify@2.1.1	None	0	39.7 kB	matteo.collina
npm/jest@29.7.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+237	18.6 MB	simenb
npm/prettier@3.2.5	environment, filesystem, unsafe	0	8.39 MB	prettier-bot
npm/source-map-support@0.5.21	filesystem	+2	895 kB	linusu

🚮 Removed packages: npm/@solana/web3.js@1.78.5, npm/@typescript-eslint/eslint-plugin@5.62.0, npm/@typescript-eslint/parser@5.62.0, npm/axios@1.7.4, npm/bs58@5.0.0, npm/dotenv@16.3.1, npm/eslint-config-prettier@8.10.0, npm/eslint-plugin-jest@27.2.3, npm/eslint-plugin-prettier@4.2.1, npm/eslint@8.49.0, npm/prettier@2.8.8, npm/src@1.1.2, npm/tronweb@4.4.0, npm/web3-core@1.9.0, npm/web3-eth-contract@1.9.0, npm/web3-utils@1.9.0, npm/web3@1.9.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
Install scripts	npm/protobufjs@7.3.0	Install script: postinstall Source: node scripts/postinstall	rest-api/package.json rest-api/pnpm-lock.yaml	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/protobufjs@7.3.0