Spectra Assure
Community
Docs
failIncident: Removal
Scanned: 4 days ago

AzureRM.Profile.Netcore

latest
removed
Top 10k
[PowerShell .Net Core] Microsoft Azure PowerShell - Profile credential management cmdlets for Azure Resource Manager
License: unknown
Published: over 7 years 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:

removal
Reported By: Community

Popularity

69.04k
Total Downloads
2
Contributors
0
Declared Dependencies
64
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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in PowerShell Gallery community

100 packages
found in
Top 100
900 packages
found in
Top 1k
8992 packages
found in
Top 10k
17108 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

Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures verify the origin and the integrity of the object they apply to. The integrity validation relies on the cryptographic strength of the encryption and the hash verification algorithm. If either of the two is considered weak by current standards, there is a chance the signed object could be maliciously modified, without triggering the integrity failure check.

Prevalence in PowerShell Gallery community

85 packages
found in
Top 100
354 packages
found in
Top 1k
1054 packages
found in
Top 10k
1674 packages
in community

Next steps

Create signatures with strong ECC key-length of at least 224 bits, or RSA key-length of at least 2048 bits, and use SHA256 as the hashing algorithm. While encryption key-length upgrade does require you to obtain a new certificate, the hashing algorithm can freely be selected during signing.
With Microsoft SignTool, you can specify the hashing algorithm using the /fd SHA256 parameter.

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)
90 packages
found in
Top 100
509 packages
found in
Top 1k
3113 packages
found in
Top 10k
5185 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)
17 packages
found in
Top 100
283 packages
found in
Top 1k
1860 packages
found in
Top 10k
3073 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
20 packages
found in
Top 100
254 packages
found in
Top 1k
1480 packages
found in
Top 10k
2391 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for AzureRM.Profile.Netcore

What is AzureRM.Profile.Netcore?

[PowerShell .Net Core] Microsoft Azure PowerShell - Profile credential management cmdlets for Azure Resource Manager. For more information about this package, visit its homepage.

Is AzureRM.Profile.Netcore malicious or is it safe to use?

The PS Gallery package AzureRM.Profile.Netcore has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is used. Visit the Issues and Behaviors sections of the analysis for more details. All versions of the AzureRM.Profile.Netcore package were removed.

Is AzureRM.Profile.Netcore popular?

The PS Gallery package AzureRM.Profile.Netcore ranks among the top 10000 projects in this community. It has 69K 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 AzureRM.Profile.Netcore once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how AzureRM.Profile.Netcore behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a AzureRM.Profile.Netcore 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.