Spectra Assure

failIncident: Malware

Scanned:

000webhost-api-client

malicious

License: Permissive (MIT)

Published:

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

2 malware-like behaviors found

Malware

4 supply chain attack artifacts

IMPORTANT: All versions of this package have been malicious

Latest malware incident detected:

Version: 999.9.9

INCIDENTS FOR THIS VERSION:

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: ReversingLabs (Researcher)

Learn more about malware detection

malware

Reported By: Community (Snyk)

More info

malware

Reported By: Community (NPM)

More info

malware

Reported By: Community (GitHub Advisory)

More info

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

Policies

Info

Count

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious components. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks. It is common to have multiple supply chain attack artifacts that relate to a single malware incident.

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

18 packages

found in

Top 10k

14717 packages

in community

Next steps

If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

SQ30109

Detected presence of malicious files through analyst-vetted file reputation.

Causes risk: analyst-vetted malware found

threats

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.

TH15108

Detected presence of files with behaviors that match the infostealer malware profile.

Causes risk: malware-like behaviors found

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. While most behaviors are benign, some are exclusively used by malicious software with the intent to cause harm. When a software package matches behavior traits of malicious software, it becomes flagged by security solutions. It is highly likely that the software package was tampered with by a malicious actor or a rogue insider. Detected threat type matches the behaviors typically exhibited by the infostealer malware profile. Infostealers are commonly used to steal sensitive user data such as stored login details, financial information, and other personally identifiable information.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

2 packages

found in

Top 10k

10214 packages

in community

Next steps

Investigate reported detections.

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

You should delay the software release until the investigation is completed.

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

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.

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.

TH30113

Detected presence of software components with unusual package versions.

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. Developers that use open source components within their applications can specify the exact version of the component their application depends on. However, since components are frequently updated, some developers opt to always use the latest version of the software component. This helps reduce the number of vulnerabilities that open source components can introduce in the application. However, it does expose the developer and the build environment to risks associated with software supply chain attacks. Should a threat actor hijack the ownership of the software component publishing account, or even its publishing token, they could issue a malicious update that can infect the build environment or the application itself. To ensure that the build system updates the software component to a malicious version, threat actors often set the version number to an unusually high value. If a build system is instructed to use the latest component version, it will install the component with the highest version number, and execute its code.

Prevalence in npm community

No prevalence information at this time

Next steps

Review software component versions to ensure there were no accidental code updates.

If the software component versions differ from expected, investigate the build and release environment for software supply chain compromise.

Consider pinning the software component version to prevent accidental code updates.

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.

TH16106

Detected presence of files that collect and exfiltrate user information.

hunting

Problem

Prevalence in npm community

1 packages

found in

Top 100

1 packages

found in

Top 1k

26 packages

found in

Top 10k

12384 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

Consider limiting the collection of user information to a minimum.

TH17122

Detected presence of files containing URLs related to IP querying services.

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. When accessing the internet, a device is assigned a unique Internet Protocol (IP) address. This address identifies the point of origin and destination of each request a connected device makes. Attackers often aim to better understand their targets. Collecting basic reconnaissance information typically includes the IP address of a machine. While the operating system has the utilities to get this information, some attackers may prefer getting this data from an external source. Many web services host pages that return the IP address of the caller. For that reason, attackers often opt to get the IP information from a third-party service. While the presence of IP querying services does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in npm community

0 packages

found in

Top 100

3 packages

found in

Top 1k

33 packages

found in

Top 10k

9086 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 mechanism for detecting the machine's IP address.

TH30107

Detected presence of software components that are rarely included by other public software packages.

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.

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

18 packages

found in

Top 10k

14717 packages

in community

Next steps

If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

SQ30109

Detected presence of malicious files through analyst-vetted file reputation.

Causes risk: analyst-vetted malware found

threats

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.

TH15108

Detected presence of files with behaviors that match the infostealer malware profile.

Causes risk: malware-like behaviors found

hunting

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

2 packages

found in

Top 10k

10214 packages

in community

Next steps

Investigate reported detections.

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

You should delay the software release until the investigation is completed.

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

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.

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.

TH30113

Detected presence of software components with unusual package versions.

hunting

Problem

Prevalence in npm community

No prevalence information at this time

Next steps

Review software component versions to ensure there were no accidental code updates.

If the software component versions differ from expected, investigate the build and release environment for software supply chain compromise.

Consider pinning the software component version to prevent accidental code updates.

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.

TH16106

Detected presence of files that collect and exfiltrate user information.

hunting

Problem

Prevalence in npm community

1 packages

found in

Top 100

1 packages

found in

Top 1k

26 packages

found in

Top 10k

12384 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

Consider limiting the collection of user information to a minimum.

TH17122

Detected presence of files containing URLs related to IP querying services.

hunting

Problem

Prevalence in npm community

0 packages

found in

Top 100

3 packages

found in

Top 1k

33 packages

found in

Top 10k

9086 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 mechanism for detecting the machine's IP address.

TH30107

Detected presence of software components that are rarely included by other public software packages.

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.