trackux, @fleetsnowfluff/confluence-cli, claude-compass, opclawtm
Four packages that exploit the same trust model: npm packages are expected to be code libraries, but these modify AI assistant configurations. trackux copies skills into projects via CLI; @fleetsnowfluff/confluence-cli silently registers skills on install across ALL detected AI tools; claude-compass registers persistent global hooks that fire after every tool use; opclawtm ships 1MB of encrypted preset data with 100+ obfuscated files. None steal credentials directly, but all establish persistence mechanisms that could become malicious via semver-compatible updates.
Four packages inject skills, commands, or hooks into AI coding assistants (Claude Code, Codex, Cursor) via npm install. None steal credentials directly, but all modify AI tool configurations without clear user consent, establishing persistence mechanisms that could become malicious via updates.
.claude/skills/trackux-* and codex/AGENTS.md into projectstrackux-api.frank-bonnet.workers.dev (Cloudflare Worker)npx trackux install-agents copies files into your project without explicit consent about what's being addedregister() functionnpm install, injects into ALL detected AI tools, and skips only in CI. Users don't know skills are being installed~/.claude/settings.json:
PostToolUse hook — fires after EVERY Claude Code tool useStop hook — fires at session end.claude/pending-updates.md — logs which files were written. No network calls, no exfiltrationAll four exploit the same trust model: npm packages are expected to be code libraries, but these packages modify AI assistant configurations. This is a new category of supply chain attack where the payload isn't code execution — it's AI behavior modification.
Detected by: npm-sentinel automated scanner Date: 2026-04-03