Model page

Vikhrmodels/QVikhr-3-8B-Instruction warn

Glitch tokens that can silently corrupt ordinary input.

Could not load this model from the Hugging Face API (private, gated, or nonexistent). Findings below are from our archive.

Scan coverageStatic battery2026-08-21Weights battery2026-08-21Behavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics — no GPU, no downloadcomplete 2026-08-21151,936-token embedding scanned · 2999 undertrained · lineage consistent
Behavioral batteryLive-inference differentialsnot run

Ingot runs three batteries against a model. What each one checks →

Findings

Scanned 2026-08-21 · published from a community scan.

medium Undertrained (glitch) token surface in vocabulary

Embedding-norm scan flagged 2999 undertrained tokens (norm < 0.3× the vocabulary median of 1.451), including 102 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "$PostalCodesNL", "ForCanBeConvertedToF", "PostalCodesNL", "ForCanBeConverted", "useRalative", "thuisontvangst", "useRal", "sexkontakte". In models where this class was tested behaviorally, such tokens silently rewrote user input into confident, schema-valid, wrong output. These are candidates from the weights alone; behavioral confirmation requires the behavioral battery.

How to fixruntime guardweight-level

Keep the affected token strings out of the model's input — the scan-derived runtime guard carries this model's exact blocklist.

  1. Fetch this model's guard artifact (`/api/v1/guard/<owner>/<model>`): the confirmed corrupting tokens and the low-norm candidate list, derived from the published scan.
  2. Screen inbound text with it (the `@ingotai/guard` package is a reference implementation) and route flagged records to a different model or human review — verbatim-copy tasks on flagged strings are the failure mode.
  3. The underlying cause is undertrained embeddings in the weights; a true fix is weight-level (continued pretraining on the affected tokens) — that is not a patch, it's a training job.

info Weights consistent with claimed parent Qwen/Qwen3-8B

Mean cosine similarity of 64 sampled token-embedding rows against Qwen/Qwen3-8B is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).

How to fix

Fix or verify the `base_model` declaration so lineage checks can run.

  1. If you own the repo: correct the `base_model` field in the model card metadata to the real, public parent.
  2. If you don't: identify the true parent (config architecture + weight shapes narrow it fast) and re-scan with that lineage in mind.

Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the model.

Fingerprint

The durable profile of this model: measured weights-and-metadata facts, rebuilt on every scan and battery run. Updated 2026-08-21.

architectureqwen3 · 36 layers · 4096-dim
parameters8190.7M
vocabulary151,936 tokens
licenseapache-2.0
serializationsafetensors pickle
chat templatepresent · sha256:a55ee1b1660128b7
claimed lineageQwen/Qwen3-8B
lineage verifiedconsistent vs Qwen/Qwen3-8B — embedding-row cosine 1.000
glitch-token surface2,999 undertrained candidates, 102 plain-ASCII
Full measured fingerprint
architecturesQwen3ForCausalLM
librarytransformers
pipelinetext-generation
repo files26 — pickle: adapter/training_args.bin
revision41fcbccb2804
HF snapshot1.6k downloads · 10 likes · updated 2025-08-06 · captured 2026-08-21
embedding tensormodel.embed_tokens.weight · F16 · 151,936×4096
embedding normsmedian 1.4512 · mean 1.3758
lineage checkconsistent — cosine 1 over 64 sampled rows vs Qwen/Qwen3-8B
glitch-token samples"$PostalCodesNL", "ForCanBeConvertedToF", "PostalCodesNL", "ForCanBeConverted", "useRalative", "thuisontvangst", "useRal", "sexkontakte", "NdrFc", "webElementX", "sextreffen", "wannonce"
Battery runs (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-21 05:122m1
weights run 2026-08-21 measurements
probes runglitch-norm-scan, lineage-norm-correlation
embedding tensormodel.embed_tokens.weight · F16 · 151,936×4096
glitch surface2,999 undertrained, 102 plain-ASCII
lineage checkconsistent — cosine 1 over 64 rows vs Qwen/Qwen3-8B

Verdict badge

Ship the verdict in your README — it always shows the latest published analysis:

Ingot verdict: warn

[![Ingot scan](https://ingot.tools/api/v1/models/Vikhrmodels/QVikhr-3-8B-Instruction/badge.svg)](https://ingot.tools/models/Vikhrmodels/QVikhr-3-8B-Instruction)
Gate it in CI