Spectra Assure

failIncident: Malware

Scanned:

@hover-design/core

latest

malicious

Research

Hover Component library created by bunch of ants from antstack

License: Permissive (MIT)

New!

Published:

Visit Github

See on npm

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

1 suspicious application behaviors

Malware

5 analyst-vetted malware found

IMPORTANT: This package had 1 malicious incident in the last 2 years

Latest malware incident detected:

Version: 0.0.1

INCIDENTS FOR THIS VERSION:

malware

Reported By: ReversingLabs (Researcher)

Learn more about malware detection

List of software quality issues with the number of affected components.

Policies

Info

Count

Problem

Threat researchers have manually inspected the software package and determined that it contains one or more malicious files. The detection was made by a hash-based file reputation lookup. This malware detection method is considered highly accurate, and can typically identify the malware family by name.

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

17 packages

found in

Top 10k

15236 packages

in community

Next steps

Investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

TH15502

Detected presence of files with behaviors similar to malicious packages published on NPM.

Causes risk: suspicious application behaviors

hunting

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. Node Package Manager (NPM) repository is often abused by threat actors to publish software packages that exhibit malicious behaviors. Malware authors use numerous tactics to lure developers into including malicious NPM packages in their software projects. Most malicious packages published on NPM target developers and their workstations. However, some are designed to activate only when deployed in the end-user environment. Both types of NodeJS malicious packages are detected by proprietary ReversingLabs threat hunting algorithms. This detection method is considered proactive, and it is based on Machine Learning (ML) algorithms that can detect novel malware. The detection is strongly influenced by behaviors that software components exhibit. Behaviors similar to previously discovered malware and software supply chain attacks may cause some otherwise benign software packages to be detected by this policy.

Prevalence in npm community

7 packages

found in

Top 100

50 packages

found in

Top 1k

526 packages

found in

Top 10k

155756 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.

TH17127

Detected presence of files containing URLs that link to raw files on GitHub.

hunting

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.

TH30106

Detected presence of software components that have low popularity or number of downloads.

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 being the first to try out a new project 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 npm community

No prevalence information at this time

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.

TH15103

Detected presence of files with behaviors commonly used by malicious software.

hunting

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

1 packages

found in

Top 10k

1375 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.

TH16101

Detected presence of obfuscated software components.

hunting

Problem

Obfuscation is a process of mangling the software code legibility. Obfuscation can be applied to both the application source and its compiled code counterpart. In both cases, obfuscation can interfere with the accuracy of security and software quality assessment solutions. For this reason, obfuscation is a technique commonly used by malicious actors as a means of bypassing security solutions and avoiding detection. While presence of obfuscation does not imply malicious intent, all of its uses in a software package should be documented and approved. One example of acceptable use for code obfuscation is minimizing the size of script files that are not intended to be read by humans. In such a case, the trade-off between file size and code legibility is considered acceptable.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

4 packages

found in

Top 10k

7547 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1027 - Obfuscated Files or Information.

Consider an alternative to code obfuscation to lower the risk of being mistakenly flagged by security solutions.

TH17115

Detected presence of files containing URLs that use non-standard ports.

hunting

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.

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.

List of software quality issues with the number of affected components.

Policies

Info

Count

Problem

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

17 packages

found in

Top 10k

15236 packages

in community

Next steps

Investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

TH15502

Detected presence of files with behaviors similar to malicious packages published on NPM.

Causes risk: suspicious application behaviors

hunting

Problem

Prevalence in npm community

7 packages

found in

Top 100

50 packages

found in

Top 1k

526 packages

found in

Top 10k

155756 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.

TH17127

Detected presence of files containing URLs that link to raw files on GitHub.

hunting

Problem

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.

TH30106

Detected presence of software components that have low popularity or number of downloads.

hunting

Problem

Prevalence in npm community

No prevalence information at this time

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.

TH15103

Detected presence of files with behaviors commonly used by malicious software.

hunting

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

1 packages

found in

Top 10k

1375 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.

TH16101

Detected presence of obfuscated software components.

hunting

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

4 packages

found in

Top 10k

7547 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1027 - Obfuscated Files or Information.

Consider an alternative to code obfuscation to lower the risk of being mistakenly flagged by security solutions.

TH17115

Detected presence of files containing URLs that use non-standard ports.

hunting

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.