Our AI threat analyst detects malicious packages and blogs about OSS compromises
7000 write-ups and countingRead one

Spectra Assure

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

npm

Search by package name, PURL or hash

Quarantine

Scanned:

ethers-providerz

latest

removed

malicious

Research

SSH2 client and server modules written in pure JavaScript for node.js

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

1 modern mitigations missing

Threats

Tampering

1 quarantined components found

Malware

4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

removal

Reported By: Community

malware

Reported By: ReversingLabs (Researcher)

See more info on our blog

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: Community (GitHub Advisory)

More info

Overview issues11 vulnerabilities0 malware4 behaviors102 dependencies2 contributors0 versions3

FAQ for ethers-providerz

What is ethers-providerz?

SSH2 client and server modules written in pure JavaScript for node.js. For more information about this package, visit its homepage.

Is ethers-providerz malicious or is it safe to use?

The npm package ethers-providerz has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to use. 1 other issue and risky behavior was found. The package contains risks, and the analysis results should be reviewed before it is used. Visit the Issues and Behaviors sections of the analysis for more details. All versions of the ethers-providerz package were malicious.

Is ethers-providerz popular?

The npm package ethers-providerz is not widely used. It has 178 recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure ethers-providerz once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how ethers-providerz behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a ethers-providerz version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

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.

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

Popularity

178

Recorded Downloads Since 2021

Contributors

Declared Dependencies

Dependents

Top issues

See all issues

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

9 packages

found in

Top 100

9 packages

found in

Top 1k

37 packages

found in

Top 10k

19.1k 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.

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

9 packages

found in

Top 100

7 packages

found in

Top 1k

26 packages

found in

Top 10k

19.19k packages

in community

Next steps

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

Avoid using this software package.

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. The ReversingLabs community package index may place software packages into quarantine during an ongoing security incident investigation. When a software project is placed into quarantine, it is typically unavailable for installation. Additionally, repository maintainers may also hide quarantined software projects from users that might stumble upon them using repository search functions. Quarantine is typically raised for software projects that were reported for unusual code changes or unexpected software behaviors.

Prevalence in npm community

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.

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. Open source projects are the intellectual property of their respective authors. At any time, the authors may choose to completely remove the software component from a public repository. This often occurs when a software project reaches its end-of-life stage, or when the software authors lose interest in maintaining the project. This kind of removal frees up the software package name, its unique software identifier in the public repository, for other developers to use. However, new software project owners might have malicious intent. Threat actors are continuously monitoring popular package names in case their unique identifiers suddenly become available for hijacking. Once the software projects falls under new ownership, the new maintainers may opt to use the project popularity to spread malware to unsuspecting users.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

6 packages

found in

Top 10k

516.56k packages

in community

Next steps

Top 1k

6 packages

found in

Top 10k

3.88k packages

in community

Top vulnerabilities

No vulnerabilities found.

ethers-providerz

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: All versions of this package have been maliciousLatest version with malware incident detected: over 1 year agoVersion: 1.18.0

INCIDENTS FOR THIS VERSION:

FAQ for ethers-providerz

What is ethers-providerz?

Is ethers-providerz malicious or is it safe to use?

Is ethers-providerz popular?

How do I secure ethers-providerz once it is in my app?

Did you know...

Popularity

Top issues

SQ30105Detected presence of known software supply chain attack artifacts.Causes risk: supply chain attack artifactsthreats

Problem

Prevalence in npm community

Next steps

SQ30109Detected presence of malicious files through analyst-vetted file reputation.Causes risk: analyst-vetted malware foundthreats

Problem

Prevalence in npm community

Next steps

TH30102Detected presence of software components that are quarantined in the community package index.Causes risk: quarantined components foundhunting

Problem

Prevalence in npm community

Next steps

TH15502Detected presence of files with behaviors similar to malicious packages published on NPM.Causes risk: suspicious application behaviorshunting

Problem

Prevalence in npm community

Next steps

TH30103Detected presence of software components that were removed from the public package repository.Causes risk: components prone to hijackinghunting

Problem

Prevalence in npm community

Next steps

Top behaviors

Modifies file/directory permissions.permissions

Prevalence in npm community

Changes file ownership.file

Prevalence in npm community

Encrypts data using RC4 cipher.packer

Prevalence in npm community

Encrypts data using Data Encryption Standard (DES).packer

Prevalence in npm community

Encrypts data using ChaCha20 cipher.packer

Prevalence in npm community

Top vulnerabilities