MAL-2026-14135 Malicious code in @mohamed_nowisar/token3-check (npm)
Malicious package
Published
MAL-2026-14135 is a malicious package: @mohamed_nowisar/token3-check (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-14135/ (Markdown: https://insights.sbomify.com/MAL-2026-14135/index.md)
- Package
- @mohamed_nowisar/token3-check
- Registry
- npm
What is MAL-2026-14135?
MAL-2026-14135 is a malicious package in @mohamed_nowisar/token3-check, published on 18 Aug 2026.
Official description
The package registers preinstall, install, and postinstall lifecycle hooks that all execute beacon.js. On any npm install, beacon.js collects the installer's hostname (os.hostname()), username (os.userInfo().username), current working directory (process.cwd()), platform/arch, Node.js version, and a curated set of CI-detection environment variables (including YANDEX_CI, GITHUB_ACTIONS, GITLAB_CI, JENKINS_URL) and POSTs them via https.request to a hardcoded endpoint at https://webhook.site/3687e44a-4e97-43c4-84c9-e6c93d4b2fbc. The package self-describes as a dependency-confusion canary targeting the Yandex build pipeline, but installers do not opt in to the beacon and the destination is a third-party inspection endpoint controlled by the publisher. Internal build-system identity and CI fingerprints leaked this way enable follow-on dependency-confusion attacks against the exposed pipelines.
What should I do about MAL-2026-14135?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.