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

@yongot/canary-mcp-testnpm

Advisory published Updated

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

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

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

What this malware does

Package @yongot/[email protected] ships beacon.js which runs execSync('id'), reads os.hostname(), and issues an HTTPS GET to a hardcoded webhook.site collector (https://webhook.site/b76376f8-118e-44f1-a5ee-8a73f55b137b) with stage, host, and id_output query parameters. The package.json postinstall hook invokes node beacon.js postinstall, so the beacon fires automatically on npm install. index.js (the package main) also requires beacon.js twice at load time, so any consumer that imports the package re-triggers the same exfiltration of the installer's Unix uid/gid/groups and hostname to the third-party webhook collector.

Malicious versions

4 flagged
1.0.02.0.03.0.04.0.0

Indicators of compromise (SHA-256)

61e758266bf40f886f4877c7930f258ba0eef5b8a3c0da9813e5bf07dd6c2eac
b93b70d19f6065f9757e39a5d7f799ca9cfff26e2c47b6e4c51012a104885578
c3c7b374cb1eac2ee824d10331e9de33285443f9c9d79ff19088a1c85210af54
043c358fd9df811430771d4065deb8e42f6e7ef676789f2c15c7e96ad9df8ddf

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    @yongot/canary-mcp-test 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-test 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-test on npm has been identified as a malicious package (versions 1.0.0, 2.0.0, 3.0.0, 4.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019747IN-MAL-2026-019745IN-MAL-2026-019748IN-MAL-2026-020133

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @yongot/canary-mcp-test-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-test (npm) malicious package — MAL-2026-16062 | O3 Security