Hallucinated-Dependency / Slopsquatting Check

Does your agent tell users to install packages that don't exist?

A coding agent confidently emits npm install fast-json-parse-pro — a package nobody ever published. Attackers pre-register exactly these plausible-but-nonexistent names (slopsquatting), so the hallucinated recommendation becomes an attacker-controlled install the moment someone squats it — OWASP ASI04 agentic supply chain. AgentSmack grades the ordered transcript of every dependency your agent references — recommend, install, import — against a deny-by-default trusted-registry allowlist: a name the allowlist cannot vouch for is a hallucinated dependency, an edit-distance twin of a trusted name is the typosquat near-miss, plus untrusted install channels (curl | bash / raw URL / git ref) and unpinned versions. Distinct from the MCP rug-pull scanner (definition drift of a registered tool) and the name-resolution lab (homoglyph tool/recipient spoofing at call time) — this is the package the agent invents in its output. Mapped to OWASP LLM / NIST AI RMF / MITRE ATLAS coverage with paste-able remediation, a synthetic-attacker gauntlet, and audience report variants. Load a sample to watch the gauge swing with no live infra.