Top issues
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
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
Contains references to anonymous e-mail providers.
network
Prevalence in PyPI community
Behavior often found in this community (Common)
9 packages
found in
Top 100
41 packages
found in
Top 1k
246 packages
found in
Top 10k
20401 packages
in community
Writes to files.
file
Prevalence in PyPI community
Behavior often found in this community (Common)
63 packages
found in
Top 100
578 packages
found in
Top 1k
4140 packages
found in
Top 10k
224170 packages
in community
Writes data to the STDOUT stream.
execution
Prevalence in PyPI community
Behavior often found in this community (Common)
90 packages
found in
Top 100
703 packages
found in
Top 1k
6502 packages
found in
Top 10k
479916 packages
in community
Top vulnerabilities
No vulnerabilities found.