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 RubyGems community
8 packages
found in
Top 100
59 packages
found in
Top 1k
600 packages
found in
Top 10k
4103 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 software components that are rarely included by other public software packages.
hunting
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 RubyGems community
No prevalence information at this timeNext 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 RubyGems community
27 packages
found in
Top 100
375 packages
found in
Top 1k
1571 packages
found in
Top 10k
15785 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
Contains URLs that link to raw files on GitHub.
network
Prevalence in RubyGems community
Behavior often found in this community (Common)
8 packages
found in
Top 100
59 packages
found in
Top 1k
600 packages
found in
Top 10k
4106 packages
in community
Contains URLs related to online payment services.
network
Prevalence in RubyGems community
Behavior often found in this community (Common)
1 packages
found in
Top 100
14 packages
found in
Top 1k
165 packages
found in
Top 10k
1293 packages
in community
Contains URLs that use non-standard ports.
network
Prevalence in RubyGems community
Behavior often found in this community (Common)
27 packages
found in
Top 100
376 packages
found in
Top 1k
1574 packages
found in
Top 10k
15826 packages
in community
Contains URLs related to social network URLs.
network
Prevalence in RubyGems community
Behavior often found in this community (Common)
18 packages
found in
Top 100
113 packages
found in
Top 1k
871 packages
found in
Top 10k
10579 packages
in community
Queries the current Ruby on Rails environment.
search
Prevalence in RubyGems community
Behavior often found in this community (Common)
13 packages
found in
Top 100
58 packages
found in
Top 1k
584 packages
found in
Top 10k
6161 packages
in community
Top vulnerabilities
No vulnerabilities found.