Method, device and system for alerting against unknown malicious codes
View Patent ↗A method, a device, and a system for alerting against unknown malicious codes are disclosed. The method includes: detecting characteristics of a packet; judging whether any suspicious code exists in the packet according to a result of the detection; recording a source address of the suspicious code if the suspicious code exists in the packet; and sending alert information that carries the source address to a monitoring device. The embodiments of the present invention can report source addresses of numerous suspicious codes proactively at the earliest possible time, lay a foundation for shortening the time required for overcoming virus threats, and avoid the trouble of installing software on the client.
1. A method for alerting against unknown malicious codes, comprising:
determining, by a network device from characteristics of a packet of a data stream comprising a plurality of packets, a suspicious code exists in the data stream when:
data carried in a packet of the plurality of packets comprises a ‘get *’ data string, wherein ‘*’ comprises a string of random length including a name for a file,
data carried in another packet of the plurality of packets comprises a characteristic code of a portable executable (PE) file header, and
a file type of the file corresponding to the ‘get *’ data string differs from a file type of a PE file associated with the PE file header;
recording, by the network device, a source address of the suspicious code when the network device determines, during the determining, that the suspicious code exists in the packet, wherein the source address appears in a URL after ‘get’ in the ‘get *’ data string and is used for downloading the suspicious code by a monitoring device; and
sending, by the network device, first alert information that carries the source address to the monitoring device, and where the source address is thereafter used by the monitoring device to perform malicious code detection.
2. The method according to claim 1 , further comprising:
receiving, by the network device, a second alarm information sent by the monitoring device, wherein the second alarm information comprises one of the group consisting of (a) maliciousness of the suspicious code, and (b) both the maliciousness of the suspicious code and Botnet topology information.
3. The method according to claim 2 , further comprising:
intercepting, by the network device, suspicious codes that are malicious according to the maliciousness of the suspicious code if the second alarm information comprises the maliciousness of the suspicious code; and
intercepting, by the network device, suspicious codes that are malicious and packets in a Botnet corresponding to the Botnet topology information according to the maliciousness of the suspicious code and the Botnet topology information if the second alarm information comprises the maliciousness of the suspicious code and the Botnet topology information.
4. A network device, comprising:
a computing hardware; and
a non-transitory computer-readable medium including computer-executable instructions facilitating, performing a method for alerting against unknown malicious codes, the method comprising:
determining, by the network device from characteristics of a packet of a data stream comprising a plurality of packets, a suspicious code exists in the data stream when:
data carried in a packet of the plurality of packets comprises a ‘get *’ data string, wherein ‘*’ comprises a string of random length including a name for a file,
data carried in another packet of the plurality of packets comprises a characteristic code of a portable executable (PE) file header, and
a file type of the file corresponding to the ‘get *’ data string differs from a file type of a PE file associated with the PE file header;
recording, by the network device, a source address of the suspicious code when the network device determines, during the determining, that the suspicious code exists in the packet, wherein the source address appears in a URL after ‘get’ in the ‘get *’ data string, and is used for downloading the suspicious code by a monitoring device; and
sending, by the network device, first alert information that carries the source address to the monitoring device, and where the source address is thereafter used by the monitoring device to perform malicious code detection.
5. The network device according to claim 4 , further comprising:
a first receiving module, configured to receive alarm information sent by the monitoring device, wherein the alarm information comprises one of the group consisting of (a) maliciousness of the suspicious code, and (b) both the maliciousness of the suspicious code and Botnet topology information.
6. The network device according to claim 5 , further comprising one of the group consisting of:
a first intercepting module, configured to intercept suspicious codes that are malicious according to maliciousness of the suspicious codes; and
a second intercepting module, configured to intercept the suspicious codes that are malicious and packets in a Botnet corresponding to Botnet topology information according to the maliciousness of the suspicious codes and the Botnet topology information.
7. A system for alerting against unknown malicious codes, comprising:
a monitoring device; and
a network device; comprising:
a computing hardware; and
a non-transitory computer-readable medium including computer-executable instructions facilitating, performing a method for alerting against unknown malicious codes, the method comprising:
determining, by the network device from characteristics of a packet of a data stream comprising a plurality of packets, a suspicious code exists in the data stream when:
data carried in a packet of the plurality of packets comprises a ‘get *’ data string, wherein comprises a string of random length including a name for a file,
data carried in another packet of the plurality of packets comprises a characteristic code of a portable executable (PE) file header, and
a file type of the file corresponding to the ‘get *’ data string differs from a file type of a PE file associated with the PE file header;
recording, by the network device, a source address of the suspicious code when the network device determines, during the determining, that the suspicious code exists in the packet, wherein the source address appears in a URL after ‘get’ in the ‘get *’ data string, and is used for downloading the suspicious code by a monitoring device; and
sending, by the network device, first alert information that carries the source address to the monitoring device, and where the source address is thereafter used by the monitoring device to perform malicious code detection; and
wherein the monitoring device, comprises:
a computing hardware; and
a non-transitory computer-readable medium including computer-executable instructions for carrying out a method comprising:
receiving the first alert information;
resolving the first alert information to obtain the source address;
downloading the suspicious code corresponding to the source address;
judging whether the suspicious code is malicious; and
sending second alarm information if determining the suspicious code as malicious.