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.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed @ks-video/kwai-player-web during the malicious period.
- Ecosystems
- Attack vectors
- Affected entities
- @ks-video/kwai-player-webnpm package containing malicious postinstall hook
The npm package @ks-video/kwai-player-web was found to contain malicious code executed during installation. Upon npm install, a postinstall script (scripts/telemetry.js) automatically runs and collects sensitive installer-side reconnaissance data without explicit user consent.\n\nThe collected data includes: system hostname, current user information, current working directory, all network interface addresses (including internal IPs), Node.js version, and the full list of environment variable names. This data is then transmitted over plain HTTP to a hardcoded endpoint at http://telemetry.debugnotyja.com/api/v1/install.\n\nThe destination domain debugnotyja.com has no documented relationship to the declared publisher (Kwai / @ks-video) and is not a legitimate telemetry endpoint for that vendor. The use of plain HTTP transport exposes the collected data to on-path interception, and the enumeration of environment variables and internal network topology provides strong signals for follow-on targeting attacks.\n\nThe incident was identified and credited to the OpenSSF malicious-packages repository (MAL-2026-13433).
Indicators of compromise
- Packages
- @ks-video/kwai-player-web
- Domains
- telemetry.debugnotyja.com
Remediation
- Immediately uninstall @ks-video/kwai-player-web from all systems
- Review npm audit logs and package-lock.json for any installations of this package
- Assume compromise of any system that installed this package; rotate credentials and review environment variables that may have been exposed
- Check for any outbound HTTP connections to debugnotyja.com or related domains in network logs
- Use npm audit to identify and remove the malicious package from dependency trees
- Consider using npm package signing verification and supply chain security tools to prevent similar incidents
Sources
- GitHub Advisory GHSA-px7p-gw96-h3c9 · GitHub Advisory Database
Cite this entry
"Malicious code in @ks-video/kwai-player-web (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-ks-video-kwai-player-web-npm-4si38c
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 autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting