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

bitcoinlib-dev

Artifact:
latest
malicious
Research
bitcoinlib database fixes ValueError: Old database version found (<0.4.21). Can not convert to >0.5 version database automatically, use updatedb.py tool to update
License: Permissive (MIT)
Published: 7 months ago


SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
1 active web service credentials

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

Tampering
2 malware-like behaviors found
Malware
3 supply chain attack artifacts

INCIDENTS:

malware
7 months agoReported By: ReversingLabs (Researcher)
Learn more about malware detection
malware
7 months agoReported By: Community (Snyk)

Popularity

790
Total Downloads
Contributor
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 PyPI community

0 packages
found in
Top 100
0 packages
found in
Top 1k
5 packages
found in
Top 10k
13913 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 PyPI community

0 packages
found in
Top 100
0 packages
found in
Top 1k
7 packages
found in
Top 10k
13959 packages
in community

Next steps

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

Problem

Software as a Service (SaaS) platforms expose programmable interfaces to their authenticated users. These web services enable action automation and secure exchange of information. For authorization, users provide a unique token that confirms their access rights to the web service. Access tokens for supported web services are automatically validated via the least privilege APIs the service exposes. Detected tokens have been accepted as valid by the services they are associated with. This indicates they are currently active and may be abused if exposed to the public. Web service access tokens are considered secrets. They should never be included in a software release package, even if they are obfuscated by encryption on the client-side.

Prevalence in PyPI community

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

Next steps

You should securely store web service access tokens, and fully automate their management and periodic rotation.
If tokens were published unintentionally and the software has been made public, you should revoke exposed tokens and file a security incident.
Examples of service tokens that may have been detected include AWS, Facebook, JWT, SWT, Slack and others.

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 PyPI community

0 packages
found in
Top 100
0 packages
found in
Top 1k
1 packages
found in
Top 10k
1960 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 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. Python Package Index (PyPI) repository is often abused by threat actors to publish software packages that exhibit malicious behaviors. Malware authors use numerous tactics to lure developers into including malicious PyPI packages in their software projects. Most malicious packages published on PyPI target developers and their workstations. However, some are designed to activate only when deployed in the end-user environment. Both types of Python malicious packages are detected by proprietary ReversingLabs threat hunting algorithms. This detection method is considered proactive, and it is based on Machine Learning (ML) algorithms that can detect novel malware. The detection is strongly influenced by behaviors that software components exhibit. Behaviors similar to previously discovered malware and software supply chain attacks may cause some otherwise benign software packages to be detected by this policy.

Prevalence in PyPI community

47 packages
found in
Top 100
226 packages
found in
Top 1k
1735 packages
found in
Top 10k
74797 packages
in community

Next steps

Investigate reported detections.
If the software intent does not relate to the reported behavior, investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed, or until the issue is risk accepted.
Consider rewriting the flagged code without using the marked behaviors.

Top behaviors

Prevalence in PyPI community

Behavior often found in this community (Common)
34 packages
found in
Top 100
185 packages
found in
Top 1k
1062 packages
found in
Top 10k
25867 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
39 packages
found in
Top 100
280 packages
found in
Top 1k
1754 packages
found in
Top 10k
67026 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
68 packages
found in
Top 100
508 packages
found in
Top 1k
3570 packages
found in
Top 10k
165477 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
68 packages
found in
Top 100
540 packages
found in
Top 1k
3644 packages
found in
Top 10k
154572 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
70 packages
found in
Top 100
534 packages
found in
Top 1k
3771 packages
found in
Top 10k
146071 packages
in community

Top vulnerabilities

No vulnerabilities found.