Hikvision camera admin password reset tool

It will set the camera into an 'Inactive' state, that requires you to create your own strong password to 'Activate' it.
Actually - I just realised that you are likely using the NVR PoE ports, in Plug&Play mode.
In which case, simply plug the 'Inactive' camera in to the NVR PoE port and the NVR will automatically 'Activate' it with it's own password.
 
  • Like
Reactions: Oliver010
I have a rebranded Hikvision (Knight) that has been hacked. The password has been changed and i cannot reset it.

I am not sure of the model, its a IPCAM PTZ, the firmware is V5.2.0build 140721. The serial number is being identified as HK-IPCAM071D3xxxxxxx, which doesnt look like a normal Hik serial number.

I have tried the and it says url not found.
I have tried the common passwords for hacked cameras and they arent working.
I have tried the Hikvision camera password reset utility tool
I have tried the node.js extractor tool

I havent tried the TFTP tool as i am not sure if i will brick the camera as its not "pure" hikvision.

Can anyone help please?
 
Perhaps the IP address has been changed.
Use the SADP tool to see if the camera is still responding.
There is no need to change the PC IP address for SADP to work, but if it finds that the IP address is in a different range you'll need to adjust the PC IP address to suit before you can access the camera with the browser.
Common hacked passwords are 1111aaaa asdf1234 and the original default ones are 12345 and 123456789abc
 
  • Like
Reactions: Shell820810
Perhaps the IP address has been changed.
Use the SADP tool to see if the camera is still responding.
There is no need to change the PC IP address for SADP to work, but if it finds that the IP address is in a different range you'll need to adjust the PC IP address to suit before you can access the camera with the browser.
Common hacked passwords are 1111aaaa asdf1234 and the original default ones are 12345 and 123456789abc

Thank you for the quick reply.
I can still view the camera on the ivms 4500 app,
In fact I can add it in as a new camera with the defaults and view it on the app, but not on the web browser.
it was definitely hacked, the hackers put a message on the camera.

The IP address is still ok, it's 192.168.1.200, pc is 192.168.1.65.

When I log in on the web, none of those passwords are letting me log into the web GUI (it prompts for username and password but fails). All setups etc can only be done on the web browser.
 
Last edited:
Use the SADP tool to see if the camera is still responding.
Does SADP find the camera?
Is this a model with a reset button?

I have a rebranded Hikvision (Knight)
If it really is a Hikvision OEM brand - do you have any idea what series the camera is / what Hikvision model it is based on?
If you can work that out, it may be worth re-flashing the firmware with the Hikvision tftp updater tool.
Some resources here :

This for R0 :
 
Does SADP find the camera?
Is this a model with a reset button?


If it really is a Hikvision OEM brand - do you have any idea what series the camera is / what Hikvision model it is based on?
If you can work that out, it may be worth re-flashing the firmware with the Hikvision tftp updater tool.
Some resources here :

This for R0 :
SADP does find the camera, as does IVMS. I cannot find a physical reset button and I have not been able to find a similar hikvision model.
 
Does it show the HTTP port is 80?

Can you post an image - maybe we can help you to identify it.

The tftp updater does do some validation of the firmware that's being offered for installation.
Not as much as the web GUI, but should be worth a try.

Hi

I had a look at it, seems as though the firmware was changed.

Theres text on the screen similar to an overlay (like POS).

Admin privileges has been removed and only allows video via port 8000. received "error-code-hcnetsdk-dll23" when trying to export the config.

Could not establish which corresponding Hik PTZ model it is.

A possible solution is a brute force on the camera as a last alternative.
 
Yes, you have to do that to connect to each camera.
Suggest 10.0.0.150 for connecting to camera 1
And suggest 192.168.254.100 for camera 2
Camera 2 address is typical of the range used by Hikvision NVR PoE ports.
The Camera 1 address seems anomalous - but we can sort that later once you've got the admin password.


No - the PC IP address isn't assigned by the NVR. Contrary to popular belief the Hikvision NVR doesn't provide DHCP services.
But it does manage the network configuration of any cameras that's it's been given admin access to.
The 169.254.121.85 address on the PC is a 'self-administered address' that the PC provides for itself when there is no DHCP server, and no static address defined.

OK - when you've set the PC IP address to match each target camera as suggested above, use these URLs



Hopefully you will get 2 configuration files, which you can zip up and attach here.
Do you know the hash algorithm of the encryption key?

openssl enc -d -in configurationFile -out decryptedoutput -aes-128-ecb -K 279977f62f6cfd2d91cd75b889ce0c9a -nosalt -md md5

Recent DVR firmware using the dynamic key inputted by the user when exporting the device parameter. So the above command doesn't work.
 
Do you know the hash algorithm of the encryption key?
Yes, I generated the above key for command-line OpenSSL as follows :
Code:
void make_key() {
                unsigned char data[16]="abcdefg", key[64]={0}, iv[16]={0};
                int i;
                const EVP_CIPHER *cipher = EVP_aes_128_ecb();
                EVP_CIPHER_CTX *ctx;
                EVP_BytesToKey(cipher, EVP_md5(), NULL, data, 31, 1, key, iv);
                for(i =0;i<=63; ++i) fprintf(stderr, " %x", key[i]);
                fprintf(stderr," <-- key\n");
                for(i =0;i<=15; ++i) fprintf(stderr, " %x", iv[i]);
                fprintf(stderr," <-- iv\n");
                for(i =0;i<=15; ++i) fprintf(stderr, " %x", data[i]);
                fprintf(stderr, " %s", data);
                fprintf(stderr," <--data\n");
}

Recent DVR firmware using the dynamic key inputted by the user when exporting the device parameter. So the above command doesn't work.
That's correct - the code above is for camera configuration files for firmware versions that don't use SQLlite storage for the data.
NVRs (and presumably DVRs though I've not looked) use quite different methods to encode exported configuration data, and also include individual device-specific data thta's needed to decode it.
 
Yes, I generated the above key for command-line OpenSSL as follows :
Code:
void make_key() {
                unsigned char data[16]="abcdefg", key[64]={0}, iv[16]={0};
                int i;
                const EVP_CIPHER *cipher = EVP_aes_128_ecb();
                EVP_CIPHER_CTX *ctx;
                EVP_BytesToKey(cipher, EVP_md5(), NULL, data, 31, 1, key, iv);
                for(i =0;i<=63; ++i) fprintf(stderr, " %x", key[i]);
                fprintf(stderr," <-- key\n");
                for(i =0;i<=15; ++i) fprintf(stderr, " %x", iv[i]);
                fprintf(stderr," <-- iv\n");
                for(i =0;i<=15; ++i) fprintf(stderr, " %x", data[i]);
                fprintf(stderr, " %s", data);
                fprintf(stderr," <--data\n");
}


That's correct - the code above is for camera configuration files for firmware versions that don't use SQLlite storage for the data.
NVRs (and presumably DVRs though I've not looked) use quite different methods to encode exported configuration data, and also include individual device-specific data thta's needed to decode it.

Thank you @alastairstevenson.
Please share the method for decrypting the NVRs configuration file.
 
I'm wondering if this would work for your DVR, maybe worth a try :
 
Hi All,

I have a Hik DS-7608NI-E2/8P NVR that I'm trying to reset the password on. I Tried to use the generator and setting it in the SADP pw reset screen with no luck. What are my options?
Fw: V3.4.92build 170228.

Thanks.

Edit:
I attempted to use the TFTP applcation with the computer and NVR connected to a switch which failed with the following:

Connect client failutre 0.
 
Last edited: