Huihui CyberStrike OffSec 35B Abliterated needs about 22.9 GB of memory at Q4_K_M (a 21.7 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 15 quants, from 0.2 GB to 29.2 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 2.8 GB.
35B parameter Qwen35moe model with reduced safety filtering
Huihui CyberStrike OffSec 35B Abliterated is a 35.5B parameter Qwen35moe model. It is an uncensored version with reduced safety filtering. The model is available in multiple GGUF quantizations.
Good at
- reasoning
- tools
- large context
Limits
- no vision support
- reduced safety filtering
- requires careful monitoring
Best for
- research testing
- controlled environments
- LLM experimentation
Who it’s for. Developers and researchers who need a large Qwen35moe model for experimentation and are prepared to handle reduced safety filtering. The model is not recommended for production or public-facing applications.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.2 GB | 1.4 GB | Fits | Get file → | |
| Q2_K | 13.2 GB | 14.4 GB | Too big | Get file → | |
| Q3_K_S | 15.5 GB | 16.7 GB | Too big | Get file → | |
| IQ3_S | 15.6 GB | 16.8 GB | Too big | Get file → | |
| IQ3_M | 15.8 GB | 17.0 GB | Too big | Get file → | |
| Q3_K_M | 17.2 GB | 18.4 GB | Too big | Get file → | |
| Q3_K_L | 18.6 GB | 19.7 GB | Too big | Get file → | |
| IQ4_XS | 19.2 GB | 20.4 GB | Too big | Get file → | |
| Q4_0 | 20.3 GB | 21.5 GB | Too big | Get file → | |
| Q4_K_S | 20.4 GB | 21.6 GB | Too big | Get file → | |
| Q4_K_M | 21.7 GB | 22.9 GB | Too big | Get file → | |
| Q4_1 | 22.4 GB | 23.6 GB | Too big | Get file → | |
| Q5_K_S | 24.6 GB | 25.8 GB | Too big | Get file → | |
| Q5_K_M | 25.3 GB | 26.5 GB | Too big | Get file → | |
| Q6_K | 29.2 GB | 30.4 GB | Too big | Get file → |
For 8 GB VRAM, use Q2_K (file size 13.25 GB, memory 14.4 GB). For 16 GB VRAM, Q4_K_M (file size 21.71 GB, memory 22.9 GB) is suitable. For 32 GB VRAM, Q6_K (file size 29.21 GB, memory 30.4 GB) provides the highest quality.
What GPU do you need for Huihui CyberStrike OffSec 35B Abliterated?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is the main file (0.2 GB file, about 1.4 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.2 GB file, about 1.4 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.2 GB file, about 1.4 GB in use).
- 12 GB VRAM: the best quant that fits is the main file (0.2 GB file, about 1.4 GB in use).
- 16 GB VRAM: the best quant that fits is Q2_K (13.2 GB file, about 14.4 GB in use).
- 24 GB VRAM: the best quant that fits is Q4_1 (22.4 GB file, about 23.6 GB in use).
- 32 GB VRAM: the best quant that fits is Q6_K (29.2 GB file, about 30.4 GB in use).
Which Huihui CyberStrike OffSec 35B Abliterated quant should you choose?
Q4_K_M is the usual starting point for Huihui CyberStrike OffSec 35B Abliterated: it balances file size and quality well. Here it is a 21.7 GB file.
If memory is tight, the smallest file is the first one in the table at 0.2 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Huihui CyberStrike OffSec 35B Abliterated
How much VRAM does Huihui CyberStrike OffSec 35B Abliterated need?
About 22.9 GB at Q4_K_M with an 8K context window. That is the 21.7 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run Huihui CyberStrike OffSec 35B Abliterated on an 8 GB GPU?
Yes, with the smaller files: the 0.2 GB file needs about 1.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Huihui CyberStrike OffSec 35B Abliterated GGUF?
It depends on the quant: file is 0.2 GB, Q2_K is 13.2 GB, Q3_K_S is 15.5 GB, IQ3_S is 15.6 GB, IQ3_M is 15.8 GB, Q3_K_M is 17.2 GB and 9 more.
What context length does Huihui CyberStrike OffSec 35B Abliterated support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.7 GB at 8K and 2.8 GB at 32K.
Where can I download Huihui CyberStrike OffSec 35B Abliterated GGUF?
The files are on Hugging Face in the mradermacher/Huihui-CyberStrike-OffSec-35B-abliterated-i1-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Huihui CyberStrike OffSec 35B Abliterated use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run this model on 8 GB VRAM?
Use the Q2_K quant, which requires approximately 14.4 GB of VRAM at 8 k context.
Is this model safe for public use?
No. The safety filtering is significantly reduced; it should only be used in controlled environments.
Does this model support vision?
No. The model is purely text and has no vision capabilities.