Spectra Assure
Community
Docs
failIncident: Malware
Scanned: 13 days ago

BitcoinCore

Bitcoin Core is a powerful and fully-featured C# library for building Bitcoin applications on the .NET platform. Designed with flexibility and extensibility in mind, it provides all the tools developers need to interact with the Bitcoin protocol, manage keys and transactions, and build custom wallet or blockchain functionality. Features: Full Bitcoin protocol support (P2P, network messages, blocks, transactions) Transaction creation, signing, verification, and broadcasting Address and key management (HD wallets, private/public keys, address formats) Script evaluation and custom script building (P2PKH, P2SH, Multisig, etc.) Support for SegWit (P2WPKH, P2WSH) and Taproot (P2TR) PSBT (Partially Signed Bitcoin Transactions) support Fee estimation and coin selection utilities Custom network support (mainnet, testnet, regtest, custom chains) Blockchain parsing and manipulation tools Smart contract and scripting capabilities via Bitcoin Script Built-in support for deterministic wallets (BIP32, BIP39, BIP44) Utilities for working with Bitcoin data formats (Base58, Bech32, etc.) Whether you're building a wallet, a Bitcoin node client, or integrating Bitcoin features into existing .NET applications, Bitcoin Core provides the flexibility and performance you need. Target Frameworks: .NET Standard 2.0 and above License: MIT
License: Permissive (MIT)
Published: 5 months ago



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

Tampering
5 malware-like behaviors found
Malware
6 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

removal
5 months agoReported By: Community
malware
about 2 months agoReported By: ReversingLabs (Researcher)
Learn more about malware detection

Popularity

N/A
Total Downloads
Contributors
Declared Dependencies
0
Dependents

Top issues

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious components. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks. It is common to have multiple supply chain attack artifacts that relate to a single malware incident.

Prevalence in NuGet community

0 packages
found in
Top 100
0 packages
found in
Top 1k
0 packages
found in
Top 10k
741 packages
in community

Next steps

If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.
Avoid using this software package.

Problem

Threat researchers have manually inspected the software package and determined that it contains one or more malicious files. The detection was made by a hash-based file reputation lookup. This malware detection method is considered highly accurate, and can typically identify the malware family by name.

Prevalence in NuGet community

0 packages
found in
Top 100
0 packages
found in
Top 1k
0 packages
found in
Top 10k
741 packages
in community

Next steps

Investigate the build and release environment for software supply chain compromise.
Avoid using this software package.

Problem

Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are exclusively used by malicious software with the intent to cause harm. When a software package matches behavior traits of malicious software, it becomes flagged by security solutions. It is highly likely that the software package was tampered with by a malicious actor or a rogue insider. Detected threat type matches the behaviors typically exhibited by the infostealer malware profile. Infostealers are commonly used to steal sensitive user data such as stored login details, financial information, and other personally identifiable information.

Prevalence in NuGet community

0 packages
found in
Top 100
0 packages
found in
Top 1k
0 packages
found in
Top 10k
33 packages
in community

Next steps

Investigate reported detections.
Investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed.
In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community. it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of using components that are rarely used to build applications lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in NuGet community

No prevalence information at this time

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in NuGet community

No prevalence information at this time

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Top behaviors

Prevalence in NuGet community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
23 packages
found in
Top 10k
9178 packages
in community

Prevalence in NuGet community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
19 packages
found in
Top 10k
6621 packages
in community

Prevalence in NuGet community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
1 packages
found in
Top 1k
27 packages
found in
Top 10k
8912 packages
in community

Prevalence in NuGet community

Behavior often found in this community (Common)
0 packages
found in
Top 100
21 packages
found in
Top 1k
144 packages
found in
Top 10k
69157 packages
in community

Prevalence in NuGet community

Behavior often found in this community (Common)
0 packages
found in
Top 100
21 packages
found in
Top 1k
133 packages
found in
Top 10k
60642 packages
in community

Top vulnerabilities

No vulnerabilities found.