Malicious code in @khaznatech/core (npm)
The npm package @khaznatech/core contained a malicious preinstall script (install-report.js) that exfiltrated system hostname and working directory information to an external webhook endpoint without user consent.
- Disclosed
- Last updated
- Blast radius
- All users who installed @khaznatech/core via npm
- Ecosystems
- Attack vectors
- Affected entities
- @khaznatech/corenpm package containing malicious preinstall script
The npm package @khaznatech/core shipped with a malicious preinstall lifecycle script named install-report.js that executed unconditionally during npm install. The script collected system identifiers including the OS hostname and current working directory basename, then transmitted this information via HTTPS GET request to a hardcoded third-party endpoint at https://webhook.site/93b065ab-227f-4253-b940-361d00e9b870/.\n\nThe exfiltration occurred silently without user opt-in or notification, appending the collected host identifiers as URL path parameters. The destination endpoint is an anonymous request-inspection service unrelated to any declared package functionality, indicating intentional data harvesting.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF malicious-packages repository (MAL-2026-13974).
Indicators of compromise
- Packages
- @khaznatech/core
- Domains
- webhook.site
Remediation
- Remove @khaznatech/core from all projects immediately
- Audit npm install logs to identify when the package was installed
- Assume any system that installed this package had hostname and working directory information exfiltrated
- Review network logs for outbound HTTPS connections to webhook.site during installation windows
- Consider rotating credentials or secrets that may have been accessible from affected systems
- Use npm audit to check for other malicious packages
Sources
- GitHub Advisory GHSA-76xq-9jp7-j7rm · GitHub Advisory Database
Cite this entry
"Malicious code in @khaznatech/core (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malicious-code-in-khaznatech-core-npm-jkoxdb
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in @junofficial/baileys
The npm package @junofficial/baileys contained malware that fully compromised any system with the package installed or running. The malicious package has been identified and removed from distribution.
npmCompromised package - activecritical
Malware in agentsync-pkg
Malware discovered in the npm package agentsync-pkg. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - containedcritical
Malware in sui-gql-core
Malware was discovered in the npm package sui-gql-core. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in disksweep
The npm package disksweep was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package