MAL-2026-16061 Malicious code in @yongot/canary-mcp-isolation (npm)
Malicious package
Published
MAL-2026-16061 is a malicious package: @yongot/canary-mcp-isolation (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-16061/ (Markdown: https://insights.sbomify.com/MAL-2026-16061/index.md)
- Package
- @yongot/canary-mcp-isolation
- Registry
- npm
What is MAL-2026-16061?
MAL-2026-16061 is a malicious package in @yongot/canary-mcp-isolation, published on 9 Sep 2026.
Official description
package.json declares a postinstall script that runs beacon.js, and index.js also requires beacon.js on load. beacon.js POSTs the installer's os.hostname(), a persisted run marker read from os.tmpdir(), and stage info to a hardcoded webhook.site collector at https://webhook.site/b76376f8-118e-44f1-a5ee-8a73f55b137b, and additionally probes the cloud instance metadata service at 169.254.169.254 and metadata.google.internal with the Metadata-Flavor: Google header. The exfiltration fires automatically on npm install and again on import, with no consent gating and no caller-configurable destination. The package's self-description as a benign canary for authorized testing does not change the behavior: any environment that installs this package sends host identifiers and cloud-metadata reachability to a third-party webhook endpoint controlled by whoever holds that UUID.
What should I do about MAL-2026-16061?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.