Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in cktool-core

Malware was discovered in the npm package cktool-core. Systems with the package installed or running are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with cktool-core installed or running
Ecosystems
Attack vectors
Affected entities
  • cktool-core

A malware incident was identified in the npm package cktool-core, as documented in GitHub Advisory GHSA-qm37-v399-r9m5. The advisory indicates that any computer with this package installed or running should be considered fully compromised.\n\nThe malicious package grants outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system. While the package can be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nThe incident was published on 2026-07-23 via the GitHub advisory system.

Indicators of compromise

Packages
  • cktool-core

Remediation

  • Immediately remove cktool-core from all systems
  • Rotate all secrets and keys stored on affected computers from a different, unaffected computer
  • Assume full system compromise and conduct forensic analysis
  • Monitor affected systems for signs of persistent malware or backdoors
  • Review system logs and network traffic for indicators of compromise
  • Consider full system rebuild or replacement if forensic analysis confirms persistent compromise

Sources

  1. GitHub Advisory GHSA-qm37-v399-r9m5 · GitHub Advisory Database

Cite this entry

"Malware in cktool-core." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 23, 2026; last updated July 23, 2026. https://supplychainattack.org/incident/malware-in-cktool-core-12lvfy

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malware in eth-codergen

    Malware was discovered in the npm package eth-codergen. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. containedcritical

    Malware in fs-extra-core

    Malware was discovered in the npm package fs-extra-core. Systems with this package installed or running are considered fully compromised and require immediate remediation including secret rotation and package removal.

    npmCompromised package
  3. activecritical

    Malware in lychee-norm-cache

    Malware discovered in the npm package lychee-norm-cache. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  4. containedcritical

    Malware in da-sc-sdk

    Malware was discovered in the npm package da-sc-sdk. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a clean system.

    npmCompromised package