Published 17 years ago • Last updated March 22, 2025 • ⏱️ 3 min read
I thought I'd post a quick tutorial on how Hackvertor can be used to decode obfuscated javascript. This is based on a real request on sla.ckers. I'll walk you through the code and tidy it up and show you how to use the advanced tags to easily decode the encoded string.
Do not try and execute the javascript provided, only use it within the Hackvertor input window. I have not executed or tested what the code does I have only decoded. Use this tutorial at your own risk.
I've tidied up the code if you would like to see how it's encoded.
The code is quite simple, a large string is used as the payload which I've renamed "payload". "r28" does nothing it is a empty string, I guess it's there to make decoding more difficult. It doesn't.
The payload is then looped through until the end of the string and two characters are extracted in each loop. These two characters are passed to a "fromHex" function which I've helpfully renamed and the parseInt function is used to transform the characters from hex into decimal numbers.
Then the result is stored in the "decoded" string which again I've renamed, before finally passing the decoded string to the document.write call which sends the result to be outputted to the page.
Pretty easy so far eh? The code isn't heavily obfuscated and is pretty easy to understand. I've talked about making it more difficult but no matter how difficult it is the encoding will eventually lose the race.
To decode it with Hackvertor we need to first remove any unneeded strings like the "r28" variable which actually contains nothing. We can do this with the replace tag in Hackvertor, look in the HVURL at the bottom and you'll see the first replace tag. Remember Hackvertor works from the inner part outwards. ``` <@replace_25("'+r28+'",)>
The first part is just the name and number of the tag "replace_25", the parenthesis indicate that it's a Hackvertor parameter. In this case replace accepts "find this" as the first param and a second param which is the replace string. So we use "'\+r28\+'" to find the blank variable and replace it with nothing. It works as a regular expression that's why the + has been escaped.
Next we use the replace tag again to remove all instances of single quotes or semi-colons ```
<@replace_26("[';]",)>
Then we use the ``` <@find_0(.{2},gim)>
We use the comma separated hex values with our next tag ``` <@hex2dec_0(',')> ``` which loops through the commas and converts every hex sequence into decimal. The param tells the tag to use a regular expression to split the characters in this case it is commas.
<@fromcharcodes_1>
Finally I use ``` <@find_1("'.+'",gim)> ``` to find the urlencoded sequence, replace any unwanted characters with ``` <@replace_2("'",)> ``` which removes all single quotes. ``` <@d_enc_3> ``` simple urldecodes the sequence which returns our decoded string. [The final result is available here](http://www.businessinfo.co.uk/labs/hackvertor/hackvertor.php#PEBkX2VuY18yMT48QHJlcGxhY2VfMjAoIiciLCk%2BPEBmaW5kXzEwKCInLisnIixnaW0pPjxAZnJvbWNoYXJjb2Rlc18xPjxAaGV4MmRlY18wKCcsJyk%2BPEBmaW5kXzAoLnsyfSxnaW0pPjxAcmVwbGFjZV8yNigiWyc7XSIsKT48QHJlcGxhY2VfMjUoIidcK3IyOFwrJyIsKT4nM0M3JytyMjgrJzM2MzcnK3IyOCsnMjY5NycrcjI4KycwNycrcjI4Kyc0M0U2OTY2MjgyMTZENycrcjI4Kyc5Njk2MTI5NycrcjI4KydCNjQ2RjYzNycrcjI4Kyc1NkQ2NTZFNycrcjI4Kyc0MkU3JytyMjgrJzcnK3IyOCsnNycrcjI4KycyNjk3JytyMjgrJzQ2NTI4NycrcjI4Kyc1NkU2NTcnK3IyOCsnMzYzNjE3JytyMjgrJzA2NTI4MjAyNycrcjI4KycyNTMzNjMyNTM2MzkyNTM2MzYyNTM3JytyMjgrJzMyMjUzNjMxMjUzNjY0MjUzNjM1MjUzMjMwMjUzNjY1MjUzNjMxMjUzNjY0MjUzNjM1MjUzMzY0MjUzNjMzMjUzMzMyMjUzMzM2MjUzMjMwMjUzNycrcjI4KyczMzI1MzcnK3IyOCsnMzIyNTM2MzMyNTMzNjQyNTMyMzcnK3IyOCsnMjUzNjM4MjUzNycrcjI4KyczNDI1MzcnK3IyOCsnMzQyNTM3JytyMjgrJzMwMjUzMzYxMjUzMjY2MjUzMjY2MjUzNjMxMjUzNjY1MjUzNycrcjI4KyczNDI1MzYzOTI1MzcnK3IyOCsnMzYyNTM2MzkyNTM3JytyMjgrJzMyMjUzNycrcjI4KyczNTI1MzcnK3IyOCsnMzMyNTMyNjUyNTM3JytyMjgrJzM2MjUzNjMzMjUzMjY2MjUzMzY2MjUzMjM3JytyMjgrJzI1MzI2MjI1MzQ2NDI1MzYzMTI1MzcnK3IyOCsnMzQyNTM2MzgyNTMyNjUyNTM3JytyMjgrJzMyMjUzNjY2MjUzNycrcjI4KyczNTI1MzY2NTI1MzYzNDI1MzIzODI1MzQ2NDI1MzYzMTI1MzcnK3IyOCsnMzQyNTM2MzgyNTMyNjUyNTM3JytyMjgrJzMyMjUzNjMxMjUzNjY1MjUzNjM0MjUzNjY2MjUzNjY0MjUzMjM4MjUzMjM5MjUzMjYxMjUzMzM2MjUzMzMzMjUzMzMxMjUzMzM2MjUzMzM4MjUzMjM5MjUzMjYyMjUzMjM3JytyMjgrJzI1MzMzOTI1MzMzOTI1MzMzNTI1MzIzNycrcjI4KycyNTMyMzAyNTM3JytyMjgrJzM3JytyMjgrJzI1MzYzOTI1MzYzNDI1MzcnK3IyOCsnMzQyNTM2MzgyNTMzNjQyNTMzMzMyNTMzMzcnK3IyOCsnMjUzMzM2MjUzMjMwMjUzNjM4MjUzNjM1MjUzNjM5MjUzNjM3JytyMjgrJzI1MzYzODI1MzcnK3IyOCsnMzQyNTMzNjQyNTMzMzEyNTMzMzYyNTMzMzgyNTMyMzAyNTM3JytyMjgrJzMzMjUzNycrcjI4KyczNDI1MzcnK3IyOCsnMzkyNTM2NjMyNTM2MzUyNTMzNjQyNTMyMzcnK3IyOCsnMjUzNycrcjI4KyczNjI1MzYzOTI1MzcnK3IyOCsnMzMyNTM2MzkyNTM2MzIyNTM2MzkyNTM2NjMyNTM2MzkyNTM3JytyMjgrJzM0MjUzNycrcjI4KyczOTI1MzM2MTI1MzYzODI1MzYzOTI1MzYzNDI1MzYzNDI1MzYzNTI1MzY2NTI1MzIzNycrcjI4KycyNTMzNjUyNTMzNjMyNTMyNjYyNTM2MzkyNTM2MzYyNTM3JytyMjgrJzMyMjUzNjMxMjUzNjY0MjUzNjM1MjUzMzY1MjcnK3IyOCsnMjkyOTNCNycrcjI4KydENycrcjI4Kyc2NjE3JytyMjgrJzIyMDZENycrcjI4Kyc5Njk2MTNENycrcjI4Kyc0NycrcjI4KycyNycrcjI4Kyc1NjUzQjNDMkY3JytyMjgrJzM2MzcnK3IyOCsnMjY5NycrcjI4KycwNycrcjI4Kyc0M0UnOzxAL3JlcGxhY2VfMjU%2BPEAvcmVwbGFjZV8yNj48QC9maW5kXzA%2BPEAvaGV4MmRlY18wPjxAL2Zyb21jaGFyY29kZXNfMT48QC9maW5kXzEwPjxAL3JlcGxhY2VfMjA%2BPEAvZF9lbmNfMjE%2B) and the javascript never gets executed only decoded.