Top issues
Detected presence of known software supply chain attack artifacts.
Causes risk: supply chain attack artifacts
threats
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.
Detected presence of malicious files through analyst-vetted file reputation.
Causes risk: analyst-vetted malware found
threats
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.
Detected presence of files with behaviors similar to malicious packages published on PyPI.
Causes risk: suspicious application behaviors
hunting
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.
Detected presence of software components that were removed from the public package repository.
Causes risk: components prone to hijacking
hunting
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. Open source projects are the intellectual property of their respective authors. At any time, the authors may choose to completely remove the software component from a public repository. This often occurs when a software project reaches its end-of-life stage, or when the software authors lose interest in maintaining the project. This kind of removal frees up the software package name, its unique software identifier in the public repository, for other developers to use. However, new software project owners might have malicious intent. Threat actors are continuously monitoring popular package names in case their unique identifiers suddenly become available for hijacking. Once the software projects falls under new ownership, the new maintainers may opt to use the project popularity to spread malware to unsuspecting users.Prevalence in PyPI community
No prevalence information at this timeNext steps
Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
Avoid using this software package until it is vetted as safe.
Detected presence of software components that have low popularity or number of downloads.
hunting
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 being the first to try out a new project 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 PyPI community
No prevalence information at this timeNext 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
Contains Base64-encoded URLs.
anomaly
Prevalence in PyPI community
Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
2 packages
found in
Top 1k
24 packages
found in
Top 10k
759 packages
in community
Decodes data using the Base64 algorithm.
packer
Prevalence in PyPI community
Behavior often found in this community (Common)
40 packages
found in
Top 100
253 packages
found in
Top 1k
1433 packages
found in
Top 10k
53416 packages
in community
Creates a process.
execution
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
Executes a file.
execution
Prevalence in PyPI community
Behavior often found in this community (Common)
34 packages
found in
Top 100
169 packages
found in
Top 1k
1256 packages
found in
Top 10k
55955 packages
in community
Enumerates system information.
search
Prevalence in PyPI community
Behavior often found in this community (Common)
43 packages
found in
Top 100
264 packages
found in
Top 1k
1666 packages
found in
Top 10k
47165 packages
in community
Top vulnerabilities
No vulnerabilities found.