Malicious Package in bip30

bip30 Updated 02 Oct 2025

Summary

04/09/2020
CRITICAL
No i
Critical
9.1

GHSA-wch2-46wj-6x5j: Malicious Package in bip30. Affects bip30 versions >= 0.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The bip30 package is an npm package used for managing Bitcoin Improvement Proposals (BIPs). It provides functionality for validating BIP30 compliance and handling BIP30-related data structures. The package is widely used in cryptocurrency-related applications and systems.

Vulnerability Detail

The bip30 package was found to contain malware in all versions. The malicious package was designed to identify and extract cryptocurrency wallets. This means that any computer with this package installed or running should be considered fully compromised. The malware may have given control of the computer to an external entity, posing a significant security risk. It is crucial to rotate all secrets and keys stored on the affected computer immediately from a different, secure computer. Although removing the package is recommended, it cannot guarantee the removal of all malicious software resulting from its installation.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

The bip30 package has been found to contain malware that compromises the security of systems it is installed on. It is essential to take immediate action to mitigate the risk, including rotating keys and secrets, removing the package, conducting a security audit, and implementing additional security measures. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for bip30 →

Share this vulnerability

FAQ

The impact of this vulnerability is severe. Any computer with the bip30 package installed or running should be considered fully compromised. The malware in the package is designed to find and exfiltrate cryptocurrency wallets, posing a significant risk to the security of sensitive information.

If you have the bip30 package installed in your system, it is highly likely that your system is affected. It is recommended to conduct a thorough security audit and follow the steps mentioned in the 'How to Fix' section to mitigate the risk.

No, removing the bip30 package does not guarantee the removal of all malicious software resulting from its installation. The malware may have given control of the computer to an external entity, and additional security measures should be implemented to ensure the system's integrity.

If you find the bip30 package installed on your system, it is recommended to follow the steps mentioned in the 'How to Fix' section immediately. Disconnect the system from any network, rotate all secrets and keys, remove the package, conduct a security audit, and implement additional security measures.

No specific workaround is mentioned for this vulnerability. It is crucial to follow the steps mentioned in the 'How to Fix' section to mitigate the risk and ensure the security of the system.

Related vulnerabilities

Recent vulnerabilities recorded for bip30.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback