hashcat Forum › Support › hashcat v
DES Token encoding exception

Threaded Mode
DES Token encoding exception
Miragui Offline
Junior Member
**
Posts: 5
Threads: 1
Joined: Sep 2025
#1
11 hours ago
I have a problem with this DES hash that gives me a Token encoding exception.

I'm running hashcat with the following command:

hashcat.exe -m 1500 -a 3 -w 3 hash.txt ?a?a?a?a?a?a?a?a -i

It throws the following error:

hashcat (v7.1.2) starting

CUDA API (CUDA 13.0)
====================
* Device #01: NVIDIA GeForce RTX 5090, 30841/32606 MB, 170MCU

OpenCL API (OpenCL 3.0 CUDA 13.0.78) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #02: NVIDIA GeForce RTX 5090, skipped

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 8
Minimum salt length supported by kernel: 0
Maximum salt length supported by kernel: 256

Hashfile 'hash.txt' on line 1 (c6[PGXUxuoBd2): Token encoding exception
No hashes loaded.

Started: Fri Sep 05 09:18:13 2025
Stopped: Fri Sep 05 09:18:14 2025

How can I fix this?
Find
Reply
buka Offline
Member
***
Posts: 72
Threads: 0
Joined: Dec 2022
#2
11 hours ago
"[" isn't part of the DES alphabet.
Find
Reply
Miragui Offline
Junior Member
**
Posts: 5
Threads: 1
Joined: Sep 2025
#3
11 hours ago
(11 hours ago)buka Wrote: "[" isn't part of the DES alphabet.

Do you know what kind of hash it can be then? Because the autodetect won't detect it.
Find
Reply
buka Offline
Member
***
Posts: 72
Threads: 0
Joined: Dec 2022
#4
11 hours ago
What made you think it's a hash at all? Where did you get it?
Find
Reply
Miragui Offline
Junior Member
**
Posts: 5
Threads: 1
Joined: Sep 2025
#5
11 hours ago
(11 hours ago)buka Wrote: What made you think it's a hash at all? Where did you get it?

It's from a Mercedes head unit, it's from the hash table so it is a hash, but maybe some modified hash.

root:c6[PGXUxuoBd2:0:0:0
shell:HJN1iF85dz3Ro:1293840094:0:0
sys:BL0jQTmGRDIn2:1293840106:0:0
nav:3N5kliW2JsKSY:1293840115:0:0
scp:SOCc6dfKiSADw:1293840127:0:0
hmi:WQnGwnojBE0xk:1293840137:0:0
mm:4SU87ZeSfTU06:1293840150:0:0
pdTongueFBT4Q6blglPc:1293840069:0:0
ons:ODkh6Wb74a23I:1293840053:0:0
conn:5BCMEOw32KcrE:1293849462:0:0
pt:6B/B4vvyKqaKU:1293846391:0:0
Find
Reply
buka Offline
Member
***
Posts: 72
Threads: 0
Joined: Dec 2022
#6
10 hours ago
I think it was corrupted at some point, either accidentally or deliberately.
Find
Reply
Miragui Offline
Junior Member
**
Posts: 5
Threads: 1
Joined: Sep 2025
#7
10 hours ago
(10 hours ago)buka Wrote: I think it was corrupted at some point, either accidentally or deliberately.

Must be deliberate then, because I have another device that has the bracket exactly in the same spot in the hash table.
Find
Reply
DanielG Offline
Pentester
***
Posts: 211
Threads: 0
Joined: Nov 2017
#8
10 hours ago
It is the correct mode, but there is somehow one or more typo's in the first line, because there should not be a [ in it.
The rest of the hashes work (hint, username is password)
Find
Reply
Miragui Offline
Junior Member
**
Posts: 5
Threads: 1
Joined: Sep 2025
#9
10 hours ago
(10 hours ago)DanielG Wrote: It is the correct mode, but there is somehow one or more typo's in the first line, because there should not be a [ in it.
The rest of the hashes work (hint, username is password)

I don't think it's a typo, this is directly from a flash dump of the device. Here is one that is slightly different but has the bracket in the same location.

root:c6[YgflxsopH3:0:0:0
shell:HJN1iF85dz3Ro:1293840094:0:0
sys:BL0jQTmGRDIn2:1293840106:0:0
nav:3N5kliW2JsKSY:1293840115:0:0
scp:SOCc6dfKiSADw:1293840127:0:0
hmi:WQnGwnojBE0xk:1293840137:0:0
mm:4SU87ZeSfTU06:1293840150:0:0
pd:PFBT4Q6blglPc:1293840069:0:0
ons:ODkh6Wb74a23I:1293840053:0:0
conn:5BCMEOw32KcrE:1293849462:0:0
pt:6B/B4vvyKqaKU:1293846391:0:0
stunnel:R6HiSrByvzzZE:1293842066:0:0
Find
Reply