Found winrar password but wrong

[whitemerc]

So, I have a compressed archive of WinRAR (128 bit AES, SHA1) with a hash like $RAR3$*1*here_is_long_hash:33. I extracted it with rar2john. 

I launched the hashcat, algorithm 23800 and in just a few years of searching I found a password for this hash!
Hashcat put it in the file RAR3$*1*here_is_long_hash:33:found_password. And this password successfully opened the archive. 

But there is some oddity. The file in the archive is 192 kilobytes (and compressed to 40 kilobytes), but the extracted file is only 100 bytes. The archive test with this password is successful, opening is successful, but the file is damaged. Actually CRC32 is OK, size is not OK.

Is it possible that several passwords are suitable for the WinRAR archive? What should I do in this case, I would like to continue the search but I do not understand how I can use the extracted password

[zamgold]

So, I have a compressed archive of WinRAR (128 bit AES, SHA1) with a hash like $RAR3$*1*here_is_long_hash:33. I extracted it with rar2john. 

I launched the hashcat, algorithm 23800 and in just a few years of searching I found a password for this hash!
Hashcat put it in the file RAR3$*1*here_is_long_hash:33:found_password. And this password successfully opened the archive. 

But there is some oddity. The file in the archive is 192 kilobytes (and compressed to 40 kilobytes), but the extracted file is only 100 bytes. The archive test with this password is successful, opening is successful, but the file is damaged. Actually CRC32 is OK, size is not OK.

Is it possible that several passwords are suitable for the WinRAR archive? What should I do in this case, I would like to continue the search but I do not understand how I can use the extracted password

The algorithm is based on checking the crc32 checksum. 4 bytes of checksum can be expanded into a huge number of equivalent values. Looks like this is a false password, use other attacks to break it