reddit.com via Reddit

LLMs fabricate identical Qwen 3 72B model specs

hallucinations open source hallucinations local-llm model-catalog

Key insights

  • At least 39 independent catalog pages fabricated matching specs for Qwen 3 72B, a model Alibaba never released.
  • The hallucinated entries shared identical details including Apache 2.0 licensing, 131k context window, and a September 2025 date.
  • The finding shows LLM-generated content can propagate coordinated misinformation across unconnected tooling systems without human oversight.

Why this matters

Model catalog integrity is now a supply-chain problem: any tool, agent, or pipeline that auto-populates model metadata from LLM-generated sources can inherit fabricated specifications and pass them downstream as facts. For founders building on top of third-party model registries or documentation generators, this exposes a concrete audit gap where fictional models could be selected, compared, or deployed against. For technical leaders, it illustrates that hallucination containment is no longer just a single-model problem but an ecosystem-level failure mode that compounds across interconnected AI tooling.

Summary

Dozens of AI tools and model index sites have independently hallucinated the same fictional model: Qwen 3 72B, a large language model that was never released. A developer auditing their own catalog discovered 39 separate pages confidently describing it, complete with an Apache 2.0 license, a September 2025 release date, and a 131k context window. Alibaba's Qwen 3 lineup skipped 72B entirely, jumping from 30B to a 235B mixture-of-experts architecture. The convergence is what makes this alarming. Multiple independent tools, documentation generators, and catalog sites fabricated matching fictional entries without coordination, suggesting these systems are drawing on the same contaminated training data or cross-referencing each other's outputs. Essentially: (Alibaba/Qwen, the broader open-source tooling ecosystem) are caught in a hallucination propagation loop. - 39 catalog pages described the same non-existent model with internally consistent but fabricated specifications. - The fabricated details are specific enough to be actionable, making them more dangerous than vague hallucinations. - The r/LocalLLaMA thread has prompted a wave of self-audits across the developer community. When hallucinations are specific, consistent, and cross-platform, they become indistinguishable from ground truth to anyone who does not already know the answer.

Potential risks and opportunities

Risks

  • Developers who integrated 'Qwen 3 72B' into automated model-selection pipelines before auditing may have shipped documentation, pricing estimates, or compliance assessments based on fictional specifications.
  • Model index platforms (Hugging Face, Ollama library, OpenRouter) face reputational risk if phantom entries persist publicly and are cited in downstream enterprise procurement decisions.
  • The same hallucination pattern likely affects other model families where parameter counts are non-contiguous, making undiscovered phantom entries a standing risk across any AI catalog that was LLM-generated or LLM-assisted.

Opportunities

  • Model registry verification services or open-source audit tooling that cross-references catalog entries against official vendor release pages could gain immediate traction given the r/LocalLLaMA visibility.
  • Alibaba/Qwen and other frontier labs could differentiate on trust by publishing machine-readable, signed model release manifests that catalogers and tooling vendors can validate against.
  • Enterprise AI governance vendors (Weights and Biases, Galileo, Arize AI) can expand their audit surface to include model metadata provenance, positioning catalog integrity checks as a compliance feature for regulated industries.

What we don't know yet

  • Whether the contaminated training data originated from a single widely-scraped source that seeded all downstream tools simultaneously, or whether each tool independently hallucinated matching specs.
  • Which specific documentation generators and model index platforms have confirmed phantom entries as of May 2026, and whether any have published remediation steps.
  • Whether Alibaba/Qwen has issued any official guidance to catalog maintainers or tooling vendors to help distinguish real from fabricated model entries.