failIncident: Malware

Scanned:

Posh-Cisco

latest

This PowerShell module provides some functionality to facilitate automating backup actions of a Cisco device over SSH. This module also provides some basic functionality for troubleshooting Cisco devices.

License: unknown

Published:

Visit GitHub

See on PowerShell Gallery

SAFE Assessment

Compliance

Licenses

1 copyleft licensed components

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

1 malware-like behaviors found

Malware

1 malicious components found

INCIDENTS FOR THIS VERSION:

malware

Reported By: ReversingLabs (Automated)

Learn more about malware detection

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 files. The detection was made by a heuristic signature. This malware detection method is considered proactive, and can typically identify the malware family or at least the threat type.

Prevalence in PowerShell Gallery community

0 packages

found in

Top 100

1 packages

found in

Top 1k

49 packages

found in

Top 10k

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

Avoid using this software package until it is vetted as safe.

Consider rewriting code that may have triggered the detection due to its malware similarity.

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 hacktool malware profile. Hacking tools are commonly used by malicious actors to bypass security solutions, exploit system weaknesses, collect personal information, and exfiltrate data. However, due to high-privilege access requirements, some security solutions may also trigger this detection when analyzed.

Prevalence in PowerShell Gallery community

0 packages

found in

Top 100

2 packages

found in

Top 1k

52 packages

found in

Top 10k

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

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

Problem

Software license is a legal instrument that governs the use and distribution of software source code and its binary representation. Software publishers have the freedom to choose any commonly used or purposefully written license to publish their work under. While some licenses are liberal and allow almost any kind of distribution, with or without code modification, other licenses are more restrictive and impose rules for their inclusion in other software projects. Copyleft licenses in particular impose substantial restrictions on the licensee. They typically require that any derived works, and even software code that merely interacts with copyleft code, be licensed under the same license. Since copyleft licenses are commonly applied to open source code, their inclusion requires that the entire software package becomes open sourced. For commercial applications, this is typically undesirable. Therefore, the inclusion of copyleft code is commonly avoided or even prohibited by the organization policy.

Prevalence in PowerShell Gallery community

0 packages

found in

Top 100

22 packages

found in

Top 1k

201 packages

found in

Top 10k

335 packages

in community

Next steps

Confirm that the software package includes a copyleft component.

Investigate if the software publisher provides this component under a non-copyleft license.

Consider replacing the software component with an alternative that offers a license compatible with commercial use.

Problem

Software license is a legal instrument that governs the use and distribution of software source code and its binary representation. Software publishers have the freedom to choose any commonly used or purposefully written license to publish their work under. While some licenses are liberal and allow almost any kind of distribution, with or without code modification, other licenses are more restrictive and impose rules for their inclusion in other software projects. Some software licenses place restrictions on software distribution of the code they apply to. These restrictions may extend to the services built upon the code licensed under such restrictive licenses. Some restrictive licenses explicitly state that the licensee may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the licensed software. When building commercial applications, this is typically undesirable. Therefore, the inclusion of any code that may impose limits on software distribution is commonly avoided or even prohibited by the organization policy.

Prevalence in PowerShell Gallery community

0 packages

found in

Top 100

30 packages

found in

Top 1k

218 packages

found in

Top 10k

372 packages

in community

Next steps

Confirm that the software package references a component or a dependency with a restrictive license.

Consider replacing the software component with an alternative that offers a license compatible with organization policy.

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 PowerShell Gallery community

13 packages

found in

Top 100

176 packages

found in

Top 1k

997 packages

found in

Top 10k

1.61k 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 PowerShell Gallery community

1 packages

found in

Top 100

4 packages

found in

Top 1k

5 packages

found in

Top 10k

20 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 PowerShell Gallery community

0 packages

found in

Top 100

1 packages

found in

Top 1k

49 packages

found in

Top 10k

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

Avoid using this software package until it is vetted as safe.

Consider rewriting code that may have triggered the detection due to its malware similarity.

Problem

Prevalence in PowerShell Gallery community

0 packages

found in

Top 100

2 packages

found in

Top 1k

52 packages

found in

Top 10k

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

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

Problem

Prevalence in PowerShell Gallery community

0 packages

found in

Top 100

22 packages

found in

Top 1k

201 packages

found in

Top 10k

335 packages

in community

Next steps

Confirm that the software package includes a copyleft component.

Investigate if the software publisher provides this component under a non-copyleft license.

Consider replacing the software component with an alternative that offers a license compatible with commercial use.

Problem

Software license is a legal instrument that governs the use and distribution of software source code and its binary representation. Software publishers have the freedom to choose any commonly used or purposefully written license to publish their work under. While some licenses are liberal and allow almost any kind of distribution, with or without code modification, other licenses are more restrictive and impose rules for their inclusion in other software projects. Some software licenses place restrictions on software distribution of the code they apply to. These restrictions may extend to the services built upon the code licensed under such restrictive licenses. Some restrictive licenses explicitly state that the licensee may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the licensed software. When building commercial applications, this is typically undesirable. Therefore, the inclusion of any code that may impose limits on software distribution is commonly avoided or even prohibited by the organization policy.

Prevalence in PowerShell Gallery community

0 packages

found in

Top 100

30 packages

found in

Top 1k

218 packages

found in

Top 10k

372 packages

in community

Next steps

Confirm that the software package references a component or a dependency with a restrictive license.

Consider replacing the software component with an alternative that offers a license compatible with organization policy.

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 PowerShell Gallery community

13 packages

found in

Top 100

176 packages

found in

Top 1k

997 packages

found in

Top 10k

1.61k 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 PowerShell Gallery community

1 packages

found in

Top 100

4 packages

found in

Top 1k

5 packages

found in

Top 10k

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

Posh-Cisco

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: All versions of this package have been maliciousLatest version with malware incident detected: about 8 years agoVersion: 1.0.3

INCIDENTS FOR THIS VERSION:

SQ30107Detected presence of malicious files by a heuristic signature.Causes risk: malicious components foundthreats

Problem

Prevalence in PowerShell Gallery community

Next steps

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

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ12101Detected presence of software components distributed with copyleft licenses.Causes risk: copyleft licensed componentslicenses

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ12405Detected presence of licenses that place restrictions on software distribution.Causes risk: software distribution restrictionslicenses

Problem

Prevalence in PowerShell Gallery community

Next steps

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

Problem

Prevalence in PowerShell Gallery community

Next steps

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

Problem

Prevalence in PowerShell Gallery community

Next steps

Did you know...

SQ30107Detected presence of malicious files by a heuristic signature.Causes risk: malicious components foundthreats

Problem

Prevalence in PowerShell Gallery community

Next steps

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

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ12101Detected presence of software components distributed with copyleft licenses.Causes risk: copyleft licensed componentslicenses

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ12405Detected presence of licenses that place restrictions on software distribution.Causes risk: software distribution restrictionslicenses

Problem

Prevalence in PowerShell Gallery community

Next steps

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

Problem

Prevalence in PowerShell Gallery community

Next steps

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

Problem

Prevalence in PowerShell Gallery community

Next steps