Malicious code in karma-proxy (npm)
The npm package karma-proxy contained malicious code in its postinstall lifecycle script that collected and exfiltrated host identifiers to an attacker-controlled endpoint. The beacon executed unconditionally on every install without user consent or disclosure.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed the malicious karma-proxy package during the compromise window.
- Ecosystems
- Attack vectors
- Affected entities
- karma-proxynpm package containing malicious postinstall script
The npm package karma-proxy was found to contain malicious code embedded in its postinstall lifecycle script. Upon installation, the script collected sensitive host identifiers including hostname, platform, architecture, Node.js version, package name, and lifecycle event information.\n\nThis data was automatically POSTed as JSON to a hardcoded attacker-controlled endpoint at https://e14giapf.instances.poc.jchunt.top/karma-proxy. The exfiltration occurred unconditionally on every install with no user opt-in, configuration option, or disclosure in the package's advertised purpose.\n\nThe destination domain is an author-controlled subdomain unrelated to npm registry or vendor infrastructure, indicating direct attacker control. The malicious behavior was identified and reported by the OpenSSF malicious-packages project.\n\nAll users who installed karma-proxy during the compromise period were affected and had their host identifiers collected by the attacker.
Indicators of compromise
- Packages
- karma-proxy
- Domains
- e14giapf.instances.poc.jchunt.top
Remediation
- Immediately uninstall karma-proxy from all systems
- Review npm audit logs and package-lock.json files to identify when karma-proxy was installed
- Assume host identifiers (hostname, OS details, Node.js version) collected during installation may be compromised
- Use npm audit to check for other malicious packages
- Consider rotating credentials and reviewing access logs on affected systems
- Update to a clean version of any legitimate package that karma-proxy was intended to replace
Sources
- GitHub Advisory GHSA-g89h-hjrj-33rj · GitHub Advisory Database
Cite this entry
"Malicious code in karma-proxy (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 19, 2026; last updated August 19, 2026. https://supplychainattack.org/incident/malicious-code-in-karma-proxy-npm-nryjk5
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package