kodiak2kv1.0.19

malicious

Copy SHA256

License: Permissive (ISC)

Repository

npm

Homepage

Published:

PublicsTestRepo

Fail

Incident: Malware

4 supply chain attack artifacts

Incidents

Type: malwareReported By: Community (Snyk)Reported: over 1 year ago

Type: malwareReported By: Community (NPM)Reported: over 1 year ago

Type: malwareReported By: Community (GitHub Advisory)Reported: over 1 year ago

Type: malwareReported By: ReversingLabs (Researcher) Reported: over 1 year ago

Learn more about malware detection

Type: malwareReported By: Community (OpenSSF)Reported: over 1 year ago

Type: malwareReported By: ReversingLabs (Automated) Reported: 2 months ago

Learn more about malware detection

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

1 severe vulnerabilities exploited

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

4 supply chain attack artifacts

Downloads

1.34K

Recorded Downloads Since 2021

Maintenance

Contributor

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for kodiak2k

What is kodiak2k?

PublicsTestRepo. For more information about this package, visit its homepage.

Is kodiak2k malicious or is it safe to use?

The npm package kodiak2k 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. 1 other issue and risky behavior was 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 kodiak2k package were malicious.

Is kodiak2k popular?

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

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