reproduction-hardhatv1.0.7

malicious

Copy SHA256

License: unknown

npm

Published:

Fail

Incident: Malware

4 supply chain attack artifacts

Incidents

Type: malwareReported By: Community (OpenSSF)Reported: about 2 months ago

Type: malwareReported By: Community (Snyk)Reported: about 1 month ago

Type: malwareReported By: Community (NPM)Reported: about 1 month ago

Type: malwareReported By: Community (GitHub Advisory)Reported: about 1 month ago

Type: malwareReported By: ReversingLabs (Researcher) Reported: about 1 month ago

Learn more about malware detection

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

Downloads

678

Recorded Downloads Since 2021

Maintenance

Contibutors

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for reproduction-hardhat

Is reproduction-hardhat malicious or is it safe to use?

The npm package reproduction-hardhat was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to download and use. 2 other issues and risky behaviors were found. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is reproduction-hardhat popular?

The npm package reproduction-hardhat is not widely used. It has 678 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 reproduction-hardhat once it is in my app?

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