Spectra Assure

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

npm

Search by package name, PURL or hash

failIncident: Malware

Scanned:

synckit

removed

malicious

Top 10k

Research

Perform async work synchronously in Node.js using `worker_threads` with first-class TypeScript support.

License: Permissive (MIT)

Published:

Visit GitHub

See on npm

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

1 patch mandated vulnerabilities

Hardening

2 low priority mitigations absent

Threats

Tampering

1 malware-like behaviors found

Malware

3 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware

Reported By: Community (Socket)

More info

malware

Reported By: Community (Bleeping Computer)

More info

removal

Reported By: Community

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: ReversingLabs (Researcher)

See more info on our blog

Overview issues14 vulnerabilities20 malware5 behaviors86 dependencies1 contributors2 versions55

Popularity

2.63B

Recorded Downloads Since 2021

Contributors

Declared Dependencies

458

Dependents

Top issues

See all issues

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious components. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks. It is common to have multiple supply chain attack artifacts that relate to a single malware incident.

Prevalence in npm community

9 packages

found in

Top 100

9 packages

found in

Top 1k

37 packages

found in

Top 10k

19.1k packages

in community

Next steps

If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

Problem

Threat researchers have manually inspected the software package and determined that it contains one or more malicious files. The detection was made by a hash-based file reputation lookup. This malware detection method is considered highly accurate, and can typically identify the malware family by name.

Prevalence in npm community

9 packages

found in

Top 100

7 packages

found in

Top 1k

26 packages

found in

Top 10k

19.19k packages

in community

Next steps

Investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Available threat intelligence telemetry has confirmed that the reported vulnerabilities are actively being exploited by malicious actors. Regulatory body or a government agency has issued a patching mandate for all software components affected by the identified vulnerabilities.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

38 packages

found in

Top 10k

12.69k packages

in community

Next steps

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.

Prevalence in npm community

24 packages

found in

Top 100

101 packages

found in

Top 1k

1359 packages

found in

Top 10k

511.03k packages

in community

Next steps

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Available threat intelligence telemetry has confirmed that the reported vulnerabilities are actively being exploited by malicious actors. Malware code that propagates through these vulnerabilities has been created. This increases the chance of automated malware attacks affecting the software component users.

Prevalence in npm community

2 packages

found in

Top 100

3 packages

found in

Top 1k

160 packages

found in

Top 10k

196.76k packages

in community

Next steps

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Top behaviors

CVE-2025-9086h

CVE-2026-5773h

1 (1 Fixable)

CVE-2025-54313h

1 (1 Fixable)

CVE-2025-54313h

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

FAQ for synckit

What is synckit?

Perform async work synchronously in Node.js using `worker_threads` with first-class TypeScript support. For more information about this package, visit its homepage.

Is synckit malicious or is it safe to use?

The npm package synckit has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to use. 2 other issues and risky behaviors were found. The package contains risks, and the analysis results should be reviewed before it is used. Visit the Issues and Behaviors sections of the analysis for more details. The package synckit had 1 incidents in versions published within 2 years prior to the latest.

Is synckit popular?

The npm package synckit ranks among the top 10000 projects in this community. It has 3B 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 synckit once it is in my app?

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

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

Popularity

2.63B

Recorded Downloads Since 2021

Contributors

Declared Dependencies

458

Dependents

Top issues

See all issues

Problem

Prevalence in npm community

9 packages

found in

Top 100

9 packages

found in

Top 1k

37 packages

found in

Top 10k

19.1k packages

in community

Next steps

If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

Problem

Prevalence in npm community

9 packages

found in

Top 100

7 packages

found in

Top 1k

26 packages

found in

Top 10k

19.19k packages

in community

Next steps

Investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

38 packages

found in

Top 10k

12.69k packages

in community

Next steps

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Prevalence in npm community

24 packages

found in

Top 100

101 packages

found in

Top 1k

1359 packages

found in

Top 10k

511.03k packages

in community

Next steps

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Available threat intelligence telemetry has confirmed that the reported vulnerabilities are actively being exploited by malicious actors. Malware code that propagates through these vulnerabilities has been created. This increases the chance of automated malware attacks affecting the software component users.

Prevalence in npm community

2 packages

found in

Top 100

3 packages

found in

Top 1k

160 packages

found in

Top 10k

196.76k packages

in community

Next steps

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Top behaviors

CVE-2025-9086h

CVE-2026-5773h

1 (1 Fixable)

CVE-2025-54313h

1 (1 Fixable)

CVE-2025-54313h

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

synckit

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: This package had 1 malicious incident in versions published within 2 years prior to the latestLatest version with malware incident detected: about 1 year agoVersion: 0.11.9

INCIDENTS FOR THIS VERSION:

Popularity

Top issues

SQ30105Detected presence of known software supply chain attack artifacts.Causes risk: supply chain attack artifactsthreats

Problem

Prevalence in npm community

Next steps

SQ30109Detected presence of malicious files through analyst-vetted file reputation.Causes risk: analyst-vetted malware foundthreats

Problem

Prevalence in npm community

Next steps

SQ31101Detected presence of patch mandated vulnerabilities.Causes risk: patch mandated vulnerabilitiesvulnerabilities

Problem

Prevalence in npm community

Next steps

SQ31102Detected presence of severe vulnerabilities with active exploitation.Causes risk: actively exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in npm community

Next steps

SQ31103Detected presence of malware-exploited vulnerabilities.Causes risk: malware exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in npm community

Next steps

Top behaviors

Writes to directories managed by package managers.file

Prevalence in npm community

Deletes files in Windows system directories.file

Prevalence in npm community

Contains common certificate strings.settings

Prevalence in npm community

Contains URLs that link to raw files on GitHub.network

Prevalence in npm community

Encrypts or encodes files and other data using the Windows Cryptography API.file

Prevalence in npm community

Top vulnerabilities

FAQ for synckit

What is synckit?

Is synckit malicious or is it safe to use?

Is synckit popular?

How do I secure synckit once it is in my app?

Did you know...

Popularity

Top issues

SQ30105Detected presence of known software supply chain attack artifacts.Causes risk: supply chain attack artifactsthreats

Problem

Prevalence in npm community

Next steps

SQ30109Detected presence of malicious files through analyst-vetted file reputation.Causes risk: analyst-vetted malware foundthreats

Problem

Prevalence in npm community

Next steps

SQ31101Detected presence of patch mandated vulnerabilities.Causes risk: patch mandated vulnerabilitiesvulnerabilities

Problem

Prevalence in npm community

Next steps

SQ31102Detected presence of severe vulnerabilities with active exploitation.Causes risk: actively exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in npm community

Next steps

SQ31103Detected presence of malware-exploited vulnerabilities.Causes risk: malware exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in npm community

Next steps

Top behaviors

Writes to directories managed by package managers.file

Prevalence in npm community

Deletes files in Windows system directories.file

Prevalence in npm community

Contains common certificate strings.settings

Prevalence in npm community

Contains URLs that link to raw files on GitHub.network

Prevalence in npm community

Encrypts or encodes files and other data using the Windows Cryptography API.file

Prevalence in npm community