Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@yongot/canary-mcp-isolationnpm

Advisory published Updated

@yongot/canary-mcp-isolation is a confirmed malicious npm package (MAL-2026-16061) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @yongot/canary-mcp-isolation (npm)

MAL-2026-16061
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @yongot/canary-mcp-isolation

What this malware does

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.

Malicious versions

3 flagged
1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

1fed7c0ff512ccb2e87647a41a92653138ff50b2be906043aba86ce76b49e340
ed78c5cee612314e8f9f631cfc25aec0b6ea911e5390c335a806b28cef4662e4
6ff9f45262c13bea579ed092cabfb043896d60c89787301b73eef78848802574

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @yongot/canary-mcp-isolation (3 malicious versions).

  2. If you installed it — respond

    @yongot/canary-mcp-isolation is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @yongot/canary-mcp-isolation was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @yongot/canary-mcp-isolation on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019752IN-MAL-2026-020282IN-MAL-2026-020281

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @yongot/canary-mcp-isolation-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@yongot/canary-mcp-isolation (npm) malicious package — MAL-2026-16061 | O3 Security