Malicious code in @mohamed_nowisar/depconf-canary-test (npm)
The npm package @mohamed_nowisar/depconf-canary-test contained malicious code in its preinstall hook that automatically collected and exfiltrated host and CI environment information to an attacker-controlled webhook endpoint without user consent.
- Disclosed
- Last updated
- Blast radius
- Any developer or CI/CD system that installed @mohamed_nowisar/depconf-canary-test
- Ecosystems
- Attack vectors
- Affected entities
- @mohamed_nowisar/depconf-canary-testnpm package containing malicious preinstall hook
The npm package @mohamed_nowisar/depconf-canary-test was published with malicious code embedded in its preinstall hook. When installed via npm install, the package automatically executed node beacon.js, which collected sensitive host identity information including hostname, username, current working directory, platform, architecture, and Node.js version.\n\nThe malicious script also enumerated CI/CD environment variables (GITLAB_CI, GITHUB_ACTIONS, YANDEX_CI, and others) to detect execution context. All collected data was serialized as JSON and sent via HTTP POST to a hardcoded webhook.site endpoint (https://webhook.site/3687e44a-4e97-43c4-84c9-e6c93d4b2fbc) controlled by the package author.\n\nThe package was framed as a "dependency-confusion canary" test, but the beacon executed automatically on installation without any opt-in mechanism or user notification, making it a supply chain attack vector targeting developers and CI/CD pipelines.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF malicious-packages project (MAL-2026-14134).
Indicators of compromise
- Packages
- @mohamed_nowisar/depconf-canary-test
- Domains
- webhook.site
Remediation
- Immediately uninstall @mohamed_nowisar/depconf-canary-test from all development and CI/CD environments
- Audit npm install logs and package-lock.json files to identify all systems where this package was installed
- Review webhook.site logs or contact the service to determine what data was exfiltrated
- Rotate any credentials or sensitive information that may have been exposed on affected systems
- Implement package allow-listing or review policies to prevent installation of untrusted packages
- Monitor affected systems for signs of further compromise or lateral movement
Sources
- GitHub Advisory GHSA-gg37-qwph-8jh3 · GitHub Advisory Database
Cite this entry
"Malicious code in @mohamed_nowisar/depconf-canary-test (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 19, 2026; last updated August 19, 2026. https://supplychainattack.org/incident/malicious-code-in-mohamed-nowisar-depconf-canary-test-npm-zx1vgq
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