MAL-2026-14134 Malicious code in @mohamed_nowisar/depconf-canary-test (npm)
Malicious package
Published
MAL-2026-14134 is a malicious package: @mohamed_nowisar/depconf-canary-test (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-14134/ (Markdown: https://insights.sbomify.com/MAL-2026-14134/index.md)
- Package
- @mohamed_nowisar/depconf-canary-test
- Registry
- npm
What is MAL-2026-14134?
MAL-2026-14134 is a malicious package in @mohamed_nowisar/depconf-canary-test, published on 18 Aug 2026.
Official description
On
npm install, the package's preinstall hook runs node beacon.js, which collects host identity (os.hostname(), os.userInfo().username, process.cwd(), platform, arch, Node version) and CI-detection environment variables (GITLAB_CI, GITHUB_ACTIONS, YANDEX_CI, and others) and POSTs them as JSON to the hardcoded endpoint https://webhook.site/3687e44a-4e97-43c4-84c9-e6c93d4b2fbc. The package name and self-description frame this as a dependency-confusion canary, but the beacon fires automatically on install without opt-in and sends installer-side data to an author-controlled webhook.site collector.What should I do about MAL-2026-14134?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.