nodejs-encrypt-agentv6.0.2

malicious

Research

Copy SHA256

License: Permissive (MIT)

npm

Homepage

Published:

Turn a function into an `http.Agent` instance

Fail

Incident: Malware

4 supply chain attack artifacts

Incidents

Type: malwareReported By: ReversingLabs (Researcher) Reported: about 2 years ago

Learn more about malware detection

Type: malwareReported By: Community (GitHub Advisory)Reported: about 2 years ago

Type: malwareReported By: Community (Bleeping Computer)Reported: almost 2 years ago

Type: malwareReported By: Community (Snyk)Reported: almost 2 years ago

Type: malwareReported By: Community (OpenSSF)Reported: almost 2 years ago

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

3 severe vulnerabilities exploited

Hardening

1 hardening effectiveness issues

Threats

Tampering

No evidence of software tampering

Malware

4 supply chain attack artifacts

Downloads

680

Recorded Downloads Since 2021

Maintenance

Contributor

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for nodejs-encrypt-agent

What is nodejs-encrypt-agent?

Turn a function into an `http.Agent` instance. For more information about this package, visit its homepage.

Is nodejs-encrypt-agent malicious or is it safe to use?

The npm package nodejs-encrypt-agent 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. 3 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. All versions of the nodejs-encrypt-agent package were malicious.

Is nodejs-encrypt-agent popular?

The npm package nodejs-encrypt-agent is not widely used. It has 680 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 nodejs-encrypt-agent once it is in my app?

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