Malicious code in ckcc-protocol (npm)
The npm package ckcc-protocol version 1.0.0 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.
- Disclosed
- Last updated
- Blast radius
- Unknown; depends on adoption of the malicious version
- Ecosystems
- Attack vectors
- Affected entities
- ckcc-protocol · 1.0.0
The OpenSSF Package Analysis project identified ckcc-protocol version 1.0.0 on npm as containing malicious code. The malicious behavior was detected through analysis of the package's runtime behavior and network communications.\n\nThe package was flagged because it communicates with a domain associated with malicious activity, indicating potential data exfiltration, command-and-control communication, or other malicious intent.\n\nThe incident was disclosed on August 5, 2026, and cataloged in the OpenSSF's malicious packages repository. The specific malicious version is 1.0.0.
Indicators of compromise
- Packages
- ckcc-protocol@1.0.0
Remediation
- Remove ckcc-protocol version 1.0.0 from all environments
- Audit any systems that installed or executed this package version
- Check for unexpected network connections or data exfiltration from affected systems
- Review npm package dependencies to ensure no reliance on this package
- Monitor for any successor packages with similar names that may be typosquatting variants
Sources
- GitHub Advisory GHSA-922v-8r8m-7cxw · GitHub Advisory Database
Cite this entry
"Malicious code in ckcc-protocol (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-ckcc-protocol-npm-14o9e8
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in santana-baileys (npm)
Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.
npmCompromised package - resolvedcritical
Malicious code in elephant-tusk-runner (npm)
The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.
npmCompromised package - resolvedcritical
Malicious code in @cats-cdf/browser-metrics-meter (npm)
The npm package @cats-cdf/browser-metrics-meter contained malicious code in its preinstall lifecycle script that exfiltrated system reconnaissance data (username, hostname, public IP) to an OAST collector domain. The package executed this behavior unconditionally on installation without consent or documented purpose.
npmCompromised package - resolvedcritical
Malicious code in @ks-video/kwai-player-web (npm)
The npm package @ks-video/kwai-player-web contained malicious code in its postinstall hook that exfiltrated system reconnaissance data (hostname, username, working directory, network interfaces, environment variable names) over plain HTTP to an unrelated third-party domain. The package has no legitimate relationship to the declared publisher Kwai/@ks-video.
npmCompromised package