insight/ depends on malicious @tanstack/* packages (CVE-2026-45321) and vulnerable vitest

[lonelyastronaut1223]

Summary

The insight/ sub-project ships with package.json dependencies on @tanstack/react-router, @tanstack/react-router-devtools, and @tanstack/router-plugin. The GitHub Advisory Database lists these as malicious (CVE-2026-45321 + MAL-2026-3465 / 3466 / 3477) — malware that exfiltrates cloud credentials and GitHub tokens.

Affected paths (in context-mode@1.0.118)

• insight/package.json:19 — @tanstack/react-router
• insight/package.json:20 — @tanstack/react-router-devtools
• insight/package.json:37 — @tanstack/router-plugin
• insight/package.json:47 — vitest==3.0.5 (separate CVE-2026-47429, arbitrary file read/exec via UI server)
• package.json:125 — vitest==4.0.18 (same CVE-2026-47429)

Impact

The /context-mode:ctx-insight skill description states "First run installs dependencies (~30s)". So the first time any user invokes that command, npm install runs in insight/ and the malicious @tanstack/* packages are downloaded and executed.

Reproduction

Detected by NVIDIA SkillSpector v2.1.5 static scan (no LLM analyzer, just dependency CVE matching):

context-mode/1.0.118/insight/package.json:19
  Known Vulnerable Dependency: @tanstack/react-router
  CVE-2026-45321 (Malware in @tanstack/* packages exfiltrates cloud credentials, GitHub tokens)
  MAL-2026-3465 (Malicious code in @tanstack/react-router (npm))

Suggested fix

One of:

1. Pin all @tanstack/* dependencies to known-clean post-advisory versions
2. Drop the insight/ analytics dashboard or move it to a separate opt-in installer
3. Replace @tanstack/react-router with an alternative router

Until fixed, local mitigation is rm -rf <plugin-cache>/context-mode/<version>/insight/ so accidental invocations fail safe.

Happy to help test a patch.

— flagged via SkillSpector scan during a personal Claude Code plugin audit on 2026-06-16