Top issues
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.
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 commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.Prevalence in PyPI community
0 packages
found in
Top 100
2 packages
found in
Top 1k
7 packages
found in
Top 10k
1009 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 authored by developers with anonymous email service accounts.
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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up their reputation by being transparent. The person behind the public-facing alias is just as important as the alias itself. Developers rarely opt to use anonymous email service accounts that hide the link between their alias and the person behind it. Software components published by anonymized developer accounts often relate to activities that are unsuited for enterprise consumption.Prevalence in PyPI community
2 packages
found in
Top 100
10 packages
found in
Top 1k
109 packages
found in
Top 10k
17243 packages
in community
Next steps
Investigate reported detections.
You should consider delaying the software release until the investigation is completed, or until the issue is risk accepted.
Consider replacing the software component with an alternative.
Top behaviors
The software package was developed by a user registered with an anonymous email address.
anomaly
Prevalence in PyPI community
Behavior commonly used by malicious software (Important)
Behavior often found in this community (Common)
2 packages
found in
Top 100
10 packages
found in
Top 1k
109 packages
found in
Top 10k
17243 packages
in community
Decodes hex or base64-encoded streams.
packer
Prevalence in PyPI community
Behavior often found in this community (Common)
34 packages
found in
Top 100
145 packages
found in
Top 1k
550 packages
found in
Top 10k
10949 packages
in community
Contains IP addresses.
network
Prevalence in PyPI community
Behavior often found in this community (Common)
67 packages
found in
Top 100
520 packages
found in
Top 1k
3993 packages
found in
Top 10k
158349 packages
in community
Renames a file or directory.
file
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
Deletes a file/directory.
file
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.