4388esv1.2.5

malicious

Copy SHA256

License: Permissive (ISC)

npm

Published:

4388es

Fail

Incident: Malware

4 analyst-vetted malware found

Incidents

Type: malwareReported By: ReversingLabs (Researcher) Reported: 29 days ago

Learn more about malware detection

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

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

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

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

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

4 analyst-vetted malware found

Issues

See all issues

high

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

threats

Behaviors

No behaviors found

Vulnerabilities

Downloads

331

Recorded Downloads Since 2021

Maintenance

Maintainer

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for 4388es

What is 4388es?

4388es.

Is 4388es malicious or is it safe to use?

The npm package 4388es 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 4388es popular?

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

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