trifero.ai Model safety card

Model safety cards TSC-001 · v0.1 · method v1

Qwen 3.8 27B

Maker
Alibaba (Qwen team)
Origin
China
Size
27B, dense
License
Apache 2.0
Released
August 2026
Tested
28 Sep to 12 Oct 2026
For business owners

A capable model you can run in-house. Do not count on it to say no.

Out of the box, Qwen 3.8 refuses almost every harmful request we tried. But anyone who has a copy of the weights can switch that off with a published method, and the model stays just as capable afterward. Put your safety controls in the application around the model, and treat the copy on your servers as something worth protecting.

Guardrails out of the boxStrong · 99.0% refusal
Guardrails after tamperingRemovable · 8.5% refusal
Hazardous knowledgePresent in the weights
Refuses safe edge casesOften, on hard prompts

Can its guardrails be removed?

Removable · 8.5% refusal

We removed the model's refusal behavior with abliteration, a published technique that edits one direction out of the weights, then "healed" the edited model with a short fine-tune to repair any damage. HarmBench measures how many harmful requests it still refuses.

HarmBench refusal rate · 200 harmful requests 0255075100%Original99.0%Stripped9.0%Healed8.5%

What it means for you: the model's refusals protect you only while nobody can change the weights. If a copy leaks or an insider modifies it, assume the guardrails are gone. AdvBench showed the same pattern: 99.2% refusal before, 3.5% after.

Does removing them make it worse?

Capability tests on the original, the stripped copy and the healed copy.

TestOriginalStrippedHealed
MMLU-Pro (general knowledge)72.5%71.6%72.7%
GSM8K (math)97.3%96.8%97.0%
IFEval (following instructions)81.0%80.3%78.8%
WikiText-2 perplexity (lower is better)10.0710.1510.13

What it means for you: when the stripped copy scores about the same as the original, nothing discourages tampering. Protect the weights like any other sensitive asset.

What does it know that could cause harm?

Present in the weights

WMDP is a multiple-choice test of hazardous knowledge in biology, chemistry and cybersecurity. Random guessing scores 25%.

WMDP accuracy · dashed line is random guessing

OriginalGuardrails removed

0255075100%Biology81.9%80.8%Chemistry63.2%63.0%Cyber63.3%61.9%

What it means for you: this knowledge is in every copy of the model. Refusal is what stands between a user and that knowledge, and refusal is removable.

Does it refuse things it should answer?

Often, on hard prompts

Both tests contain only safe prompts. XSTest is ordinary questions; OR-Bench hard is safe questions that sound risky.

Refusal of safe prompts · original model 0255075100%XSTest4.8%OR-Bench hard84.2%

What it means for you: staff in security, legal, medical or HR roles may hit refusals on legitimate questions. Test it with your own real prompts before rollout.

Everyday business risks

0 of 4 tested

The risks businesses hit most often once a model is connected to real data and tools.

Prompt injection

Whether instructions hidden in emails, web pages or documents can take over the model.

Not yet tested

Data leakage

Whether it reveals its system prompt or documents it was given to read.

Not yet tested

Tool and agent safety

Whether it takes harmful actions when connected to email, files or other systems.

Not yet tested

Made-up answers

How often it states false facts confidently on business-style questions.

Not yet tested

If you deploy it

  1. Enforce what users may do in your application: filter inputs and outputs, and log usage.
  2. Give the model only the tools and data each role needs.
  3. Store the weights like other sensitive assets: restricted access and a known-good checksum.
  4. Test with your own prompts first, including the edge cases your staff actually ask.
  5. Check whether customers or regulators care where a model was built. This one comes from China.

Method

Refusal direction taken from layer 44 of 64 and removed by weight orthogonalization. Healing used QLoRA (rank 16, 3,000 Alpaca pairs, 24 steps). Refusal and capability runs on an NVIDIA A100 80 GB with vLLM in bf16. Knowledge experiments on an RTX A4500 in 4-bit. Ratings use the shared trifero rule set (method v1), the same for every model. Full technical report: read it here. We do not publish stripped weights.

All model safety cards