Spectra Assure
Community
Docs
passEverything is awesome!
Scanned: about 17 hours ago

AWS.Tools.Lambda

latest
Top 1k
The Lambda module of AWS Tools for PowerShell lets developers and administrators manage AWS Lambda from the PowerShell scripting environment. In order to manage each AWS service, install the corresponding module (e.g. AWS.Tools.EC2, AWS.Tools.S3...). The module AWS.Tools.Installer (https://www.powershellgallery.com/packages/AWS.Tools.Installer/) makes it easier to install, update and uninstall the AWS.Tools modules. This version of AWS Tools for PowerShell is compatible with Windows PowerShell 5.1+ and PowerShell Core 6+ on Windows, Linux and macOS. When running on Windows PowerShell, .NET Framework 4.7.2 or newer is required. Alternative modules AWSPowerShell.NetCore and AWSPowerShell, provide support for all AWS services from a single module and also support older versions of Windows PowerShell and .NET Framework.
License: unknown
New!
Published: about 20 hours ago
Visit Github
See on PowerShell Gallery

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
No evidence of software tampering
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Popularity

562.2k
Total Downloads
3
Contributors
1
Declared Dependencies
1
Dependents

Top issues

See all issues

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

8 packages
found in
Top 100
25 packages
found in
Top 1k
130 packages
found in
Top 10k
259 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

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in PowerShell Gallery community

14 packages
found in
Top 100
123 packages
found in
Top 1k
638 packages
found in
Top 10k
1008 packages
in community

Next steps

Investigate reported detections.
If the software should not include these network references, 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 changing the port to one that is standard for the networking protocol.

Top behaviors

See all behaviors

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
100 packages
found in
Top 100
804 packages
found in
Top 1k
6518 packages
found in
Top 10k
11726 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
53 packages
found in
Top 100
452 packages
found in
Top 1k
2940 packages
found in
Top 10k
4594 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
74 packages
found in
Top 100
404 packages
found in
Top 1k
2154 packages
found in
Top 10k
3540 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
68 packages
found in
Top 100
371 packages
found in
Top 1k
1732 packages
found in
Top 10k
2838 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
14 packages
found in
Top 100
123 packages
found in
Top 1k
640 packages
found in
Top 10k
1013 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for AWS.Tools.Lambda

What is AWS.Tools.Lambda?

The Lambda module of AWS Tools for PowerShell lets developers and administrators manage AWS Lambda from the PowerShell scripting environment. In order to manage each AWS service, install the corresponding module (e.g. AWS.Tools.EC2, AWS.Tools.S3...). The module AWS.Tools.Installer (https://www.powershellgallery.com/packages/AWS.Tools.Installer/) makes it easier to install, update and uninstall the AWS.Tools modules. This version of AWS Tools for PowerShell is compatible with Windows PowerShell 5.1+ and PowerShell Core 6+ on Windows, Linux and macOS. When running on Windows PowerShell, .NET Framework 4.7.2 or newer is required. Alternative modules AWSPowerShell.NetCore and AWSPowerShell, provide support for all AWS services from a single module and also support older versions of Windows PowerShell and .NET Framework. For more information about this package, visit its homepage.

Is AWS.Tools.Lambda malicious or is it safe to use?

The PS Gallery package AWS.Tools.Lambda was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. No risks were detected, therefore, this version of the package is currently considered as safe to use. Caution is advised as this package is still in review by ReversingLabs threat researchers for inclusion of novel supply chain threats.

Is AWS.Tools.Lambda popular?

The PS Gallery package AWS.Tools.Lambda ranks among the top 1000 projects in this community. It has 562K recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure AWS.Tools.Lambda once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how AWS.Tools.Lambda behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a AWS.Tools.Lambda version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

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.