Malware detection method

1. A method of detecting malware on a client computer, the method comprising:

(a) generating a hash of an entity at the client computer, whereby the entity is suspected to be malware;

(b) sending the hash to a network server;

(c) considering a reputation of the hash at the network server by comparing the hash to a database of hashes of known reputation;

(d) returning results of said considering to the client computer, and, if the reputation is not known at the server, sending instructions to the client computer for obtaining further information about the entity at the client computer;

(e) obtaining said further information by executing code at the client computer already present at the client computer or sent to the client computer by the server after said considering the reputation if said code is not stored at the client computer before said generating a hash;

(f) sending the further information to the server from the client computer;

(g) analysing, at the server, the further information obtained from the client computer to determine whether a reputation can be established for the hash and, if so, storing the reputation in the database;

(h) waiting for a pre-defined length of time at the client computer for the analysis by the server to be completed before re-executing the method from step (b), wherein said waiting for a pre-defined length of time is performed by the client device inserting a timeout between steps (f) and (h), and wherein steps b to d are repeated until an indication of the completed analysis at the server is received by the client computer at the server; and

at the server, forwarding said further information to a human operator for making a decision on the reputation of the entity.

2. The method of claim 1 , further comprising executing further code at the client computer for obtaining said further information, whereby said further code is stored on the client computer before said generating a hash.

3. The method of claim 1 , wherein the hash is sent to the server over a first interface.

4. The method of claim 1 , wherein said further information is sent to the server over a second interface.

5. The method of claim 1 , wherein said code is received from the server over a third interface.

6. The method of claim 1 , further comprising storing the code on a database at the client computer.

7. The method of claim 1 , further comprising storing the further information on a database at the server for sharing a reputation of the entity with other client computers.

8. A client computer comprising:

a computer program product comprising a non-transitory computer readable medium including computer readable code which, when executed on a computer, causes the client computer to:

(a) generate a hash of an entity at the client computer, whereby the entity is suspected to be malware;

(b) send the hash to a network server;

(c) consider a reputation of the hash at the network server by comparing the hash to a database of hashes of known reputation;

(d) return results of said considering to the client computer, and, if the reputation is not known at the server, sending instructions to the client computer for obtaining further information about the entity at the client computer;

(e) obtain said further information by executing code at the client computer already present at the client computer or sent to the client computer by the server after said considering the reputation if said code is not stored at the client computer before said generating a hash;

(f) send the further information to the server from the client computer;

(g) analysis, at the server, the further information obtained from the client computer to determine whether a reputation can be established for the hash and, if so, storing the reputation in the database;

(h) wait for a pre-defined length of time at the client computer for the analysis by the server to be completed before re-executing the method from step (b), wherein said waiting for a pre-defined length of time is performed by the client device inserting a timeout between steps (f) and (h), and wherein steps b to d are repeated until an indication of the completed analysis at the server is received by the client computer; and

forward, at the server, said further information to a human operator for making a decision on the reputation of the entity.

9. The client computer of claim 8 , comprising executing further computer readable code at the client computer to cause the client computer to obtain said further information, whereby said further code is stored on the client computer before said generating a hash.

10. The client computer of claim 8 , wherein the hash is sent to the server over a first interface.

11. The client computer of claim 8 , wherein said further information is sent to the server over a second interface.

12. The client computer of claim 8 , wherein said code is received from the server over a third interface.

13. The client computer of claim 8 , further comprising the client computer is caused to store the code on a database at the client computer.

14. The client computer of claim 8 , further comprising the client computer is caused to store the further information on a database at the server for sharing a reputation of the entity with other client computers.