Huihui CyberStrike OffSec 35B Abliterated needs about 30.4 GB of memory at Q6_K (a 29.2 GB file) with an 8K context window, so it fits on a 32 GB GPU. This repository has 5 quants, from 21.7 GB (Q4_K) to 71.1 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 2.8 GB.
35B CyberStrike model fine‑tuned for precise tool‑calling in offensive‑security tasks
Huihui CyberStrike OffSec 35B Abliterated is a 35 billion‑parameter Qwen35moe model fine‑tuned for tool‑calling and vision. It emits real, structured tool calls and routes to valid agent archetypes. The model is a single‑piece merged checkpoint and is released under Apache‑2.0.
Good at
- Accurate tool‑calling for pentesting
- Structured agent routing
- Vision‑enabled task execution
Limits
- Large VRAM requirement (≈40 GB for Q4_K at 8k context)
- No safety filtering – may produce sensitive content
- Requires latest llama.cpp
Best for
- Automated pentest workflows
- Tool‑integrated security assessments
- Vision‑based reconnaissance
Who it’s for. Developers and security researchers building autonomous pentesting agents. The model is suitable for research and controlled environments, not for public or production use without review.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K | 21.7 GB | 22.9 GB | Too big | Get file → | |
| Q5_K | 25.3 GB | 26.5 GB | Too big | Get file → | |
| Q6_K | 29.2 GB | 30.4 GB | Too big | Get file → | |
| Q8_0 | 37.8 GB | 39.0 GB | Too big | Get file → | |
| BF16 | 71.1 GB | 72.3 GB | Too big | Get file → |
For 8 GB VRAM use Q4_K (21.71 GB file, ~22.9 GB memory). With 16 GB VRAM Q5_K is feasible (25.35 GB file, ~26.5 GB memory). For 32 GB VRAM Q6_K or Q8_0 can be used; Q8_0 offers higher precision at ~39 GB memory.
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: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: the best quant that fits is Q4_K (21.7 GB file, about 22.9 GB in use).
- 32 GB VRAM: the best quant that fits is Q6_K (29.2 GB file, about 30.4 GB in use).
- 48 GB VRAM: the best quant that fits is Q8_0 (37.8 GB file, about 39.0 GB in use).
Which Huihui CyberStrike OffSec 35B Abliterated quant should you choose?
Q6_K (29.2 GB) is the middle option in this repository. Very close to the original quality for most uses, at a clearly larger size than 4-bit.
If memory is tight, the smallest file is Q4_K at 21.7 GB, with the quality trade-offs that come with fewer bits. The usual sweet spot between file size and quality, and the quant most people start with.
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 30.4 GB at Q6_K with an 8K context window. That is the 29.2 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?
Not at an 8K context. The smallest file needs about 22.9 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Huihui CyberStrike OffSec 35B Abliterated GGUF?
It depends on the quant: Q4_K is 21.7 GB, Q5_K is 25.3 GB, Q6_K is 29.2 GB, Q8_0 is 37.8 GB, BF16 is 71.1 GB.
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 huihui-ai/Huihui-CyberStrike-OffSec-35B-abliterated-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?
No, the smallest quant requires ~22.9 GB memory at 8k context. 8 GB VRAM is insufficient.
Does the model support vision?
Yes, the model has detected vision ability, but no specific vision benchmark is provided.
Is the model safe for public use?
The model has reduced safety filtering; it is recommended only for research or controlled environments.