4nt3nc37v1.10.1

latest

malicious

Copy SHA256

License: unknown

npm

Homepage

Published:

README.md

Fail

Incident: Malware

suspicious components found

Incidents

Type: malwareReported By: ReversingLabs (Automated) Reported: 4 months 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

No evidence of software tampering

Malware

1 suspicious components found

Downloads

703

Recorded Downloads Since 2021

Maintenance

Maintainers

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for 4nt3nc37

What is 4nt3nc37?

README.md. For more information about this package, visit its homepage.

Is 4nt3nc37 malicious or is it safe to use?

The npm package 4nt3nc37 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. 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 4nt3nc37 popular?

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

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