hashcat Forum
Token length exception with RAR hash – what am I doing wrong? - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Token length exception with RAR hash – what am I doing wrong? (/thread-13466.html)

Token length exception with RAR hash – what am I doing wrong? - Olek_michdoch - 01-13-2026

Hello everyone,
I’m trying to crack my own RAR archive with hashcat, but I always get this error:


Token length exception
No hashes loaded.

I extracted the hash using
rar2john
. The hash starts with:


$RAR3$*1*...

So I’m using:


hashcat -m 12500 hash.txt

But no matter what I do, hashcat always says the token is too long or malformed.
What I already tried:
  • Removed the filename from the hash
  • Removed everything after the hash
  • Made sure the file contains only one single line
  • Tried different editors (Notepad, Notepad++, etc.)
  • Re-extracted the hash multiple times with rar2john
Still the same error.
Questions:
  • Is there a maximum length for RAR3 hashes in hashcat?
  • Can a very large archive produce an invalid or unsupported hash?
  • Is there a specific format that hashcat strictly expects for RAR3 hashes?
  • Could it be that the hash is incomplete or broken even though rar2john generates it?
If someone can explain exactly what causes the “Token length exception” with RAR hashes or what to check, I’d really appreciate it.
Thanks a lot!

RE: Token length exception with RAR hash – what am I doing wrong? - Olek_michdoch - 01-13-2026

I also tried mode 23800, because I thought maybe it is a compressed/encrypted container:

hashcat -m 23800 hash.txt


But I get exactly the same result.

RE: Token length exception with RAR hash – what am I doing wrong? - zamgold - 01-15-2026

Maybe, hash is too long.

RE: Token length exception with RAR hash – what am I doing wrong? - b8vr - 01-15-2026

Rar2john creates a hash like "filename:hash" if I remember correctly.  Make sure to edit out the "filename:" part.

Or if my memory on that is wrong, then it adds the filenames living inside the RAR container at the end of the hash like "hash:filename1:filename2:etc". If that's the case, edit away the filenames at the end.

Then run "hashcat --identify <hash>"

RE: Token length exception with RAR hash – what am I doing wrong? - Daniel976 - 02-02-2026

(01-13-2026, 04:52 PM)Olek_michdoch Wrote: Hello everyone,
I’m trying to crack my own RAR archive with hashcat, but I always get this error:


Token length exception
No hashes loaded.

I extracted the hash using
rar2john
. The hash starts with:


$RAR3$*1*...

So I’m using:


hashcat -m 12500 hash.txt

But no matter what I do, hashcat always says the token is too long or malformed.
What I already tried:
  • Removed the filename from the hash
  • Removed everything after the hash
  • Made sure the file contains only one single line
  • Tried different editors (Notepad, Notepad+, etc.)
  • Re-extracted the hash multiple times with rar2john
Still the same error.
Questions:
  • Is there a maximum length for RAR3 hashes in hashcat?
  • Can a very large archive produce an invalid or unsupported hash?
  • Is there a specific format that hashcat strictly expects for RAR3 hashes?
  • Could it be that the hash is incomplete or brokenhot games even though  rar2john generates it?
If someone can explain exactly what causes the “Token length exception” with RAR hashes or what to check, I’d really appreciate it.
Thanks a lot!
Let me share some experience: I also encountered the "Token length exception" with RAR3, and most of the time it was because the hash still had extra characters or line breaks. Hashcat is extremely sensitive to formatting; even a single space or unusual character can cause an error.

RE: Token length exception with RAR hash – what am I doing wrong? - b8vr - 02-02-2026

Wrong hashtype. $RAR3$*1* is mode 23700 or 23800. Run hashcat --identify hashfile to get the correct mode.

RE: Token length exception with RAR hash – what am I doing wrong? - b8vr - 02-10-2026

(Yesterday, 06:32 PM)YanTA Wrote: When I extract the hash file with the John program, its size is 2 GB and that's why HashCat can't find the password inside. Please tell me what to do. There are two movies in my zip file with a size of 700 MB.

Have you tried https://github.com/hashstation/rar2hashcat

RE: Token length exception with RAR hash – what am I doing wrong? - zamgold - 02-11-2026

I can try crack it. Write on private message

RE: Token length exception with RAR hash – what am I doing wrong? - luisadfg - 02-11-2026

Millions Lost in Crypto Every Year – Here’s Why Recovery Matters
Last month I was having coffee with a friend I hadn’t seen in a while. He looked tired. When I asked what was going on, he just stared into his cup for a second and then said quietly, “I lost everything.”
He didn’t mean he spent it all. He meant a phishing email tricked him into approving a malicious contract. In under two minutes, $87,000 in USDC and ETH vanished from his wallet. He showed me the transaction hash — clean, irreversible, gone.
I didn’t know what to say. I just listened while he told me how he spent the next three days refreshing block explorers, hoping maybe the funds would magically reappear. They didn’t.
Stories like his are everywhere. Chainalysis reported over $17 billion lost to scams and hacks in 2025 alone, and that number keeps climbing. But here’s the part most people don’t talk about: a meaningful percentage of those losses could have been at least partially recovered if the victim had acted quickly and gone to the right people.
Recovery matters because crypto isn’t like a bank account. There’s no fraud department that can reverse the wire. But the blockchain is public. Every transaction leaves footprints. When stolen funds hit an exchange that requires KYC, or when they pass through a traceable bridge, there’s often a narrow window where professionals can coordinate freezes, subpoenas, or direct returns.
My friend eventually reached out to Cryptera Chain Signals (CCS) — a professional firm that’s been doing this kind of work for 28 years. They’re not the flashy kind that promises miracles in 24 hours. They’re the methodical kind. They traced the path his funds took, identified the exchange endpoint, and helped him prepare the documentation that got a significant portion frozen before it could be fully laundered. It wasn’t 100%, but it was enough to keep him from losing his house.
The lesson he keeps repeating to anyone who’ll listen:
“Don’t wait. Don’t try to fix it yourself. And don’t trust the first person who DMs you offering help.”
Recovery isn’t always possible — but when it is, timing and expertise make all the difference. And that’s why it matters more than ever.