[Snyk] Security upgrade bcoin from 0.15.0 to 1.0.2

[adamlaska]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • packages/bitcore-lib-cash/benchmark/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	554/1000 Why? Has a fix available, CVSS 6.8	Cryptographic Issues SNYK-JS-ELLIPTIC-1064899	Yes	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Timing Attack SNYK-JS-ELLIPTIC-511941	Yes	No Known Exploit
	706/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.7	Cryptographic Issues SNYK-JS-ELLIPTIC-571484	Yes	Proof of Concept
	479/1000 Why? Has a fix available, CVSS 5.3	Regular Expression Denial of Service (ReDoS) SNYK-JS-UGLIFYJS-1727251	Yes	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: bcoin

The new version differs by 250 commits.

• 58ea98d v1.0.2
• 7647145 networks: add one more checkpoint for testnet.
• da94437 v1.0.1
• 08a04b5 net: update default mainnet seeds.
• 44e856d networks: update checkpoints and chainwork.
• b0155b6 v1.0.0
• fa84b8c pkg: update deps.
• e15d791 mtx: allow passing of preferred inputs to coin selector.
• 97e4d09 pkg: update deps.
• cfeacb3 chain: mark historical bad merkle block as mutable.
• 395811a changelog: add mention of bip151 & bip150.
• 41af7ac net: remove bip150/bip151 support.
• b6d067e consensus: fail early on pow check when target > 256 bits.
• 05c3885 net: add more aggressive dos prevention.
• 4876e80 pkg: update deps.
• 22830cf chain: earlier sanity checks.
• 1ca3738 pkg: minor.
• f826174 Merge pull request Add missing browser shim for buffertools bitpay/bitcore#525 from tuxcanfly/fix-circleci-tests
• 6cf81d3 test: fix timeout for node test
• 2eb42d6 Merge pull request Make TransactionBuilder fail if tx fee is too big bitpay/bitcore#524 from tuxcanfly/fix-circleci-tests
• 58ab9ba test: increase timeout for ci
• 5261339 Merge pull request Add "browser" field to package.json bitpay/bitcore#523 from tuxcanfly/pkg-bcrypto
• ceebd65 pkg: update bcrypto
• 21bf114 Merge pull request How do I connect to JSON-RPC? bitpay/bitcore#491 from nodar-chkuaselidze/ci

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cryptographic Issues
🦉 Regular Expression Denial of Service (ReDoS)

[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 dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, filesystem, network	+37	7.45 MB	chjj

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
Native code	npm/[email protected]	Location: Package overview	packages/bitcore-lib-cash/benchmark/package.json
Native code	npm/[email protected]	Location: Package overview	packages/bitcore-lib-cash/benchmark/package.json
Native code	npm/[email protected]	Location: Package overview	packages/bitcore-lib-cash/benchmark/package.json
Native code	npm/[email protected]	Location: Package overview	packages/bitcore-lib-cash/benchmark/package.json

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

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