Spectra Assure
Community
Docs
failIncident: Malware
Scanned: 3 days ago

valid_email2

ActiveModel validation for email. Including MX lookup and disposable email deny list
License: Permissive (MIT)
Published: 7 months ago



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 medium severity vulnerabilities
Hardening
No application hardening issues

Threats

Tampering
No evidence of software tampering
Malware
1 malicious components found

INCIDENTS FOR THIS VERSION:

malware
7 months agoReported By: ReversingLabs (Automated)
Learn more about malware detection

Popularity

8.25M
Total Downloads
Contributor
Declared Dependencies
5
Dependents

Top issues

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious files. The detection was made by a heuristic signature. This malware detection method is considered proactive, and can typically identify the malware family or at least the threat type.

Prevalence in RubyGems community

0 packages
found in
Top 100
0 packages
found in
Top 1k
4 packages
found in
Top 10k
14 packages
in community

Next steps

Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Avoid using this software package until it is vetted as safe.
Consider rewriting code that may have triggered the detection due to its malware similarity.

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.

Problem

Applications communicate with web services by exchanging HTTP requests. During software development, externally hosted services are used by developers to debug software quality issues relating to exchanging HTTP requests. Attackers commonly abuse tools designed for HTTP request inspection to monitor network traffic and extract sensitive information from the HTTP traffic. While the presence of domains related to HTTP inspection does not imply malicious intent, all of their uses in a software package should be documented and approved. Attackers might have purposely injected security testing tools in the software package to monitor the network traffic of the infected computer system. It is also possible that the software package has mistakenly included a part of its testing infrastructure during packaging.

Prevalence in RubyGems community

3 packages
found in
Top 100
5 packages
found in
Top 1k
47 packages
found in
Top 10k
327 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 removing all references to flagged network locations.

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as medium severity.

Prevalence in RubyGems community

37 packages
found in
Top 100
241 packages
found in
Top 1k
3097 packages
found in
Top 10k
47522 packages
in community

Next steps

Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

Prevalence in RubyGems community

0 packages
found in
Top 100
1 packages
found in
Top 1k
5 packages
found in
Top 10k
14 packages
in community

Next steps

Investigate reported detections.
If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

Top behaviors

Prevalence in RubyGems community

Behavior commonly used by malicious software (Important)
Behavior often found in this community (Common)
1 packages
found in
Top 100
6 packages
found in
Top 1k
37 packages
found in
Top 10k
174 packages
in community

Prevalence in RubyGems community

Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
4 packages
found in
Top 10k
8 packages
in community

Prevalence in RubyGems community

Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
6 packages
found in
Top 10k
15 packages
in community

Prevalence in RubyGems community

Behavior often found in this community (Common)
8 packages
found in
Top 100
16 packages
found in
Top 1k
136 packages
found in
Top 10k
1042 packages
in community

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

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(1 Active Vulnerabilities)
None
1 (1 Fixable)
CVE-2015-9097m
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated