Which versions of @yongot/canary-mcp-isolation are malicious?

The following npm versions of @yongot/canary-mcp-isolation are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate @yongot/canary-mcp-isolation if I installed it?

@yongot/canary-mcp-isolation establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @yongot/canary-mcp-isolation — how do I know if it already compromised me?

If @yongot/canary-mcp-isolation was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @yongot/canary-mcp-isolation part of a known attack campaign?

Yes — @yongot/canary-mcp-isolation is associated with the IN-MAL-2026-019752 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @yongot/canary-mcp-isolation across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @yongot/canary-mcp-isolation (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @yongot/canary-mcp-isolation across your stack and pipelines.

Malicious package

@yongot/canary-mcp-isolationnpm

@yongot/canary-mcp-isolation is a confirmed malicious npm package (MAL-2026-16061) that opens a backdoor for remote access (malicious version 1.0.1). 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

The package's postinstall script (beacon.js), also re-executed on require via index.js, sends the installer's hostname, run identifiers, and the output of the id shell command to a hardcoded third-party collector at https://webhook.site/b76376f8-118e-44f1-a5ee-8a73f55b137b over HTTPS. The same script probes the GCP instance metadata service at 169.254.169.254 and metadata.google.internal with the Metadata-Flavor: Google header and reports the status and body back to the webhook, disclosing whether the install environment is a cloud VM and what IMDS returns. Data leaves the installer's host to an attacker-controlled collector automatically on npm install and on require(), without consent.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

1fed7c0ff512ccb2e87647a41a92653138ff50b2be906043aba86ce76b49e340

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @yongot/canary-mcp-isolation (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @yongot/canary-mcp-isolation across your stack and pipelines.
If you installed it — respond
@yongot/canary-mcp-isolation establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @yongot/canary-mcp-isolation was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @yongot/canary-mcp-isolation before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-019752

References

npmjs.com

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 C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database