Mitigation of malware
View Patent ↗Systems and methods are provided in example embodiments for mitigating malicious calls. The system can be configured to determine a series of checksums for a file, compare the series of checksums to a checksum tree, where the checksum tree includes a plurality of nodes that each include a fuzzy checksum of known malware, and assign one or more classifications to the file, where each of the one or more classifications is based on each node of the checksum tree that matches a checksum in the series of checksums and includes whether the file includes malware or benign checksums.
1. At least one non-transitory, computer-readable medium including one or more instructions that, when executed by at least one processor, cause the at least one processor to perform a method comprising:
determining a first checksum at a first region of a first file;
comparing the first checksum to a root in a checksum tree, the root indicating a checksum at a point of a second file;
determining a second checksum at a second region of the first file offset from the first region of the first file, if the first checksum matches the root;
comparing the second checksum to a fuzzy checksum indicated by a child node of the root in the checksum tree, wherein the fuzzy checksum is of at least a portion of malware offset from the point of the second file; and
assigning a classification to the first file, if the second checksum matches the child node, the classification indicating the malware.
2. The medium of claim 1 , the method further comprising:
comparing the second checksum to another fuzzy checksum indicated by another node in the checksum tree, if the second checksum does not match the child node, the another node being a sibling to the child node.
3. The medium of claim 1 , wherein the child node indicates a numeric offset of the second region from the first region.
4. The medium of claim 1 , wherein the child node indicates a logical position of the second region.
5. The medium of claim 4 , wherein the second region is determined at an entry point of the first file, at a resources section of the first file, or a text section of the first file.
6. The medium of claim 1 , the method further comprising:
assigning a percentage to the classification.
7. The medium of claim 6 , the method further comprising:
sending a feature vector through a network, based on a comparison of the percentage and a predetermined threshold.
8. An apparatus, comprising:
a memory; and
a processor configured
to determine a first checksum at a first region of a first file;
to compare the first checksum to a root in a checksum tree, the root indicating a checksum at a point of a second file;
to determine a second checksum at a second region of the first file offset from the first region of the first file, if the first checksum matches the root;
to compare the second checksum to a fuzzy checksum indicated by a child node of the root in the checksum tree, the fuzzy checksum being of at least a portion of malware offset from the point of the second file; and
to assign a classification to the first file, if the second checksum matches the child node, the classification indicating the malware.
9. The apparatus of claim 8 , wherein the processor is further configured to compare the second checksum to another fuzzy checksum indicated by another node in the checksum tree, if the second checksum does not match the child node, the another node being a sibling to the child node.
10. The apparatus of claim 8 , wherein the child node indicates a numeric offset of the second region from the first region.
11. The apparatus of claim 8 , wherein the child node indicates a logical position of the second region.
12. The apparatus of claim 11 , wherein the second region is determined at an entry point of the first file, at a resources section of the first file, or a text section of the first file.
13. The apparatus of claim 8 , wherein the processor is further configured to assign a percentage to the classification.
14. The apparatus of claim 13 , wherein the processor is further configured to send a feature vector through a network, based on a comparison of the percentage and a predetermined threshold.
15. A method, comprising:
determining a first checksum at a first region of a first file;
comparing the first checksum to a root in a checksum tree, the root indicating a checksum at a point of a second file;
determining a second checksum at a second region of the first file offset from the first region of the first file, if the first checksum matches the root;
comparing the second checksum to a fuzzy checksum indicated by a child node of the root in the checksum tree, wherein the fuzzy checksum is of at least a portion of malware offset from the point of the second file; and
assigning a classification to the first file, if the second checksum matches the child node, the classification indicating the malware.
16. The method of claim 15 , further comprising:
comparing the second checksum to another fuzzy checksum indicated by another node in the checksum tree, if the second checksum does not match the child node, the another node being a sibling to the child node.
17. The method of claim 15 , wherein the child node indicates a numeric offset of the second region from the first region.
18. The method of claim 15 , wherein the child node indicates a logical position of the second region.
19. The method of claim 18 , wherein the second region is determined at an entry point of the first file, at a resources section of the first file, or a text section of the first file.
20. The method of claim 15 , further comprising:
assigning a percentage to the classification; and
sending a feature vector through a network, based on a comparison of the percentage and a predetermined threshold.
21. The medium of claim 1 , the method further comprising:
determining if a file location referenced at another root of another checksum tree has been analyzed, if the first checksum does not match the root in the checksum tree.
22. The medium of claim 1 , wherein the second file is an executable file, and the point of the second file is an entry point of the executable file.