Top issues
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
52 packages
found in
Top 1k
959 packages
found in
Top 10k
183909 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.
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. Top-level domains (TLD) are a part of the Domain Name System (DNS), and are used to lookup an Internet Protocol (IP) address of a requested website. There are a few different types of top-level domains. Generic, sponsored and country-code TLDs are generally accessible to the public. Registrars that govern the assignment of domain names within the TLD may choose to sell specific domain names to an interested party. However, some registrars are known to have less strict rules for assigning domain names. Attackers often abuse gaps in governance and actively seek to register their malicious domains in such TLDs. This issue is raised for all domains registered within TLDs that harbor an excessive number of malicious sites. While the presence of suspicious TLDs does not imply malicious intent, all of its uses in a software package should be documented and approved.Prevalence in npm community
5 packages
found in
Top 100
15 packages
found in
Top 1k
236 packages
found in
Top 10k
248774 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 top-level domain to avoid being flagged by security solutions.
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 npm community
6 packages
found in
Top 100
41 packages
found in
Top 1k
869 packages
found in
Top 10k
490844 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
Might contain potentially obfuscated code or data.
anomaly
Prevalence in npm community
Behavior often found in this community (Common)
21 packages
found in
Top 100
136 packages
found in
Top 1k
1248 packages
found in
Top 10k
390529 packages
in community
Encodes data using the Base64 algorithm.
packer
Prevalence in npm community
Behavior often found in this community (Common)
7 packages
found in
Top 100
61 packages
found in
Top 1k
956 packages
found in
Top 10k
319930 packages
in community
Decodes data using the Base64 algorithm.
packer
Prevalence in npm community
Behavior often found in this community (Common)
6 packages
found in
Top 100
44 packages
found in
Top 1k
657 packages
found in
Top 10k
175209 packages
in community
Contains URLs that link to raw files on GitHub.
network
Prevalence in npm community
Behavior often found in this community (Common)
10 packages
found in
Top 100
52 packages
found in
Top 1k
959 packages
found in
Top 10k
183924 packages
in community
Contains URLs that link to interesting file formats.
network
Prevalence in npm community
Behavior often found in this community (Common)
5 packages
found in
Top 100
39 packages
found in
Top 1k
518 packages
found in
Top 10k
107169 packages
in community
Top vulnerabilities
No vulnerabilities found.