Spectra Assure

failIncident: Malware

Scanned:

ctosec.appsec-wb-xray-adapter

Artifact:

latest

removed

malicious

License: unknown

Published:

See on PyPI

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

2 malware-like behaviors found

Malware

5 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: ReversingLabs (Researcher)

Learn more about malware detection

removal

Reported By: Community

malware

N/AReported By: Community (kam193)

More info

List of software quality issues with the number of affected components.

Policies

Info

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

11 packages

found in

Top 10k

14.01k 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

10 packages

found in

Top 10k

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

0 packages

found in

Top 100

0 packages

found in

Top 1k

3 packages

found in

Top 10k

2.05k 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

Most software applications use standardized installation formats for their distribution. Software installers are built from instructions written within installation scripts that act as blueprints for the distribution format assembly. Installation scripts declare the most important software properties, such as the default installation location, its external dependencies, and various actions that may occur during the installation process. Actions defined within the installation script are executed automatically during events such as software deployment, update, or removal. These events are used by software developers to set up the environment for nominal software use, or to perform cleanup upon software removal. It is unusual for certain types of software installers to execute commands that can collect sensitive system information. Attackers often abuse software installers to run commands that collect identifiable system information such as hostnames, user names, folder structures, and other data points that could help them understand the environment in which their malicious code was installed.

Prevalence in PyPI community

0 packages

found in

Top 100

1 packages

found in

Top 1k

3 packages

found in

Top 10k

706 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 installation procedure without using the marked 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

1 packages

found in

Top 100

18 packages

found in

Top 1k

104 packages

found in

Top 10k

16.5k 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.

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

0 packages

found in

Top 100

1 packages

found in

Top 1k

20 packages

found in

Top 10k

83.87k packages

in community

Next 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 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

0 packages

found in

Top 100

0 packages

found in

Top 1k

5 packages

found in

Top 10k

38.63k packages

in community

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. 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

1 packages

found in

Top 100

13 packages

found in

Top 1k

37 packages

found in

Top 10k

443.06k packages

in community

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

Prevalence in PyPI community

20 packages

found in

Top 100

92 packages

found in

Top 1k

907 packages

found in

Top 10k

43.88k 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.

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

1 packages

found in

Top 100

11 packages

found in

Top 1k

910 packages

found in

Top 10k

717.09k packages

in community

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.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

List of software quality issues with the number of affected components.

Policies

Info

Problem

Prevalence in PyPI community

0 packages

found in

Top 100

0 packages

found in

Top 1k

11 packages

found in

Top 10k

14.01k 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

Prevalence in PyPI community

0 packages

found in

Top 100

0 packages

found in

Top 1k

10 packages

found in

Top 10k

14.02k packages

in community

Next steps

Investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

Problem

Prevalence in PyPI community

0 packages

found in

Top 100

0 packages

found in

Top 1k

3 packages

found in

Top 10k

2.05k 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

Prevalence in PyPI community

0 packages

found in

Top 100

1 packages

found in

Top 1k

3 packages

found in

Top 10k

706 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 installation procedure without using the marked 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

1 packages

found in

Top 100

18 packages

found in

Top 1k

104 packages

found in

Top 10k

16.5k 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.

Problem

Prevalence in PyPI community

0 packages

found in

Top 100

1 packages

found in

Top 1k

20 packages

found in

Top 10k

83.87k packages

in community

Next 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 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

0 packages

found in

Top 100

0 packages

found in

Top 1k

5 packages

found in

Top 10k

38.63k packages

in community

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. 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

1 packages

found in

Top 100

13 packages

found in

Top 1k

37 packages

found in

Top 10k

443.06k packages

in community

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

Prevalence in PyPI community

20 packages

found in

Top 100

92 packages

found in

Top 1k

907 packages

found in

Top 10k

43.88k 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.

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

1 packages

found in

Top 100

11 packages

found in

Top 1k

910 packages

found in

Top 10k

717.09k packages

in community

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.

ctosec.appsec-wb-xray-adapter

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: All versions of this package have been maliciousLatest version with malware incident detected: 3 months agoVersion: 0.2.0

INCIDENTS FOR THIS VERSION:

SQ30105Detected presence of known software supply chain attack artifacts.Causes risk: supply chain attack artifactsthreats

Problem

Prevalence in PyPI community

Next steps

SQ30109Detected presence of malicious files through analyst-vetted file reputation.Causes risk: analyst-vetted malware foundthreats

Problem

Prevalence in PyPI community

Next steps

TH15108Detected presence of files with behaviors that match the infostealer malware profile.Causes risk: malware-like behaviors foundhunting

Problem

Prevalence in PyPI community

Next steps

TH16604Detected presence of software installers that can collect sensitive system information.Causes risk: dangerous install procedureshunting

Problem

Prevalence in PyPI community

Next steps

TH15501Detected presence of files with behaviors similar to malicious packages published on PyPI.Causes risk: suspicious application behaviorshunting

Problem

Prevalence in PyPI community

Next steps

TH30103Detected presence of software components that were removed from the public package repository.Causes risk: components prone to hijackinghunting

Problem

Prevalence in PyPI community

Next steps

TH30105Detected presence of software components that were recently published to the public package repository.hunting

Problem

Prevalence in PyPI community

Next steps

TH30106Detected presence of software components that have low popularity or number of downloads.hunting

Problem

Prevalence in PyPI community

Next steps

TH15103Detected presence of files with behaviors commonly used by malicious software.hunting

Problem

Prevalence in PyPI community

Next steps

TH30107Detected presence of software components that are rarely included by other public software packages.hunting

Problem

Prevalence in PyPI community

Next steps

Did you know...

SQ30105Detected presence of known software supply chain attack artifacts.Causes risk: supply chain attack artifactsthreats

Problem

Prevalence in PyPI community

Next steps

SQ30109Detected presence of malicious files through analyst-vetted file reputation.Causes risk: analyst-vetted malware foundthreats

Problem

Prevalence in PyPI community

Next steps

TH15108Detected presence of files with behaviors that match the infostealer malware profile.Causes risk: malware-like behaviors foundhunting

Problem

Prevalence in PyPI community

Next steps

TH16604Detected presence of software installers that can collect sensitive system information.Causes risk: dangerous install procedureshunting

Problem

Prevalence in PyPI community

Next steps

TH15501Detected presence of files with behaviors similar to malicious packages published on PyPI.Causes risk: suspicious application behaviorshunting

Problem

Prevalence in PyPI community

Next steps

TH30103Detected presence of software components that were removed from the public package repository.Causes risk: components prone to hijackinghunting

Problem

Prevalence in PyPI community

Next steps

TH30105Detected presence of software components that were recently published to the public package repository.hunting

Problem

Prevalence in PyPI community

Next steps

TH30106Detected presence of software components that have low popularity or number of downloads.hunting

Problem

Prevalence in PyPI community

Next steps