Top issues
Detected presence of web service access credentials.
Causes risk: web service credentials found
secrets
Problem
Software as a Service (SaaS) platforms expose programmable interfaces to their authenticated users. These web services enable action automation and secure exchange of information. To authenticate, web service users provide a unique account identifier and a secret that confirms their access rights. Account access credentials are considered secrets. They should never be included in a software release package, even if they are obfuscated by encryption on the client-side.Prevalence in npm community
0 packages
found in
Top 100
0 packages
found in
Top 1k
15 packages
found in
Top 10k
2.27k packages
in community
Next steps
You should securely store web service access credentials, and fully automate their management and periodic rotation.
If credentials were published unintentionally and the software has been made public, you should revoke exposed credentials and file a security incident.
Examples of service credentials that may have been detected include AWS, Square, Zoho, Duo, PayPal and others.
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. One or more embedded URLs were discovered to link to raw files hosted on GitHub. Attackers often abuse popular web services to host malicious payloads. Since code-sharing services URLs are typically allowed by security solutions, using them for payload delivery increases the odds that the malicious code will reach the user. While the presence of code-sharing service locations does not imply malicious intent, all of their uses in a software package should be documented and approved. An increasing number of software supply chain attacks in the open source space leverages the GitHub service to deliver malicious payloads.Prevalence in npm community
10 packages
found in
Top 100
53 packages
found in
Top 1k
981 packages
found in
Top 10k
194.82k 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 an alternative delivery mechanism for software packages.
Detected presence of files containing URLs that reside in regions with US export restrictions.
hunting
Problem
Export restrictions (or a restriction on exportation) are limitations on the quantity of goods exported to a specific country or countries by a Government. The United States Government has imposed export restrictions on a number of countries and regions. These restrictions may or may not apply to digital goods such as software and other related intellectual property. It is advised that the reported findings are put in the usage context so that they can be audited and reviewed by the legal department before the software package is deployed. Current list of countries with export restrictions includes: Cuba (.cu), Iran (.ir), North Korea (.nk) and Syria (.sy).Prevalence in npm community
0 packages
found in
Top 100
3 packages
found in
Top 1k
25 packages
found in
Top 10k
4.83k packages
in community
Next steps
Investigate reported detections.
You should delay the software release until the legal review is completed.
Detected presence of files containing URLs that reside in regions with EU export restrictions.
hunting
Problem
Export restrictions (or a restriction on exportation) are limitations on the quantity of goods exported to a specific country or countries by a Government. The European Union has imposed export restrictions on a number of countries and regions. These restrictions may or may not apply to digital goods such as software and other related intellectual property. It is advised that the reported findings are put in the usage context so that they can be audited and reviewed by the legal department before the software package is deployed. Current list of countries with export restrictions includes: Belarus (.by), Iran (.ir), Iraq (.iq), Libya (.ly), Myanmar (.mm), North Korea (.nk), Syria (.sy), Venezuela (.ve) and Zimbabwe (.zw).Prevalence in npm community
0 packages
found in
Top 100
5 packages
found in
Top 1k
68 packages
found in
Top 10k
13.97k packages
in community
Next steps
Investigate reported detections.
You should delay the software release until the legal review is completed.
Detected presence of licenses that place restrictions on software distribution.
Causes risk: software distribution restrictions
licenses
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 npm community
2 packages
found in
Top 100
13 packages
found in
Top 1k
198 packages
found in
Top 10k
136.34k 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.
Top behaviors
Enumerates an environment variable that holds an Amazon Web Services (AWS) session token.
search
Prevalence in npm community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
19 packages
found in
Top 10k
2.71k packages
in community
Enumerates an environment variable that holds an Amazon Web Services (AWS) secret access key.
search
Prevalence in npm community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
21 packages
found in
Top 10k
2.85k packages
in community
Enumerates an environment variable that holds an Amazon Web Services (AWS) access key.
search
Prevalence in npm community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
18 packages
found in
Top 10k
2.86k packages
in community
Modifies file/directory permissions.
permissions
Prevalence in npm community
Behavior often found in this community (Common)
6 packages
found in
Top 100
12 packages
found in
Top 1k
329 packages
found in
Top 10k
62.19k packages
in community
Might contain potentially obfuscated code or data.
anomaly
Prevalence in npm community
Behavior often found in this community (Common)
22 packages
found in
Top 100
136 packages
found in
Top 1k
1267 packages
found in
Top 10k
411.22k packages
in community
Top vulnerabilities
No vulnerabilities found.