Malware identification via secondary file analysis
A device may include one or more processors to receive a file that may be analyzed for malware; open the received file in a secure environment; determine that a secondary file in the secure environment may have been accessed based on the received file being opened; analyze the secondary file in the secure environment to identify malware; and/or perform an action associated with the received file based on the secondary file being analyzed.
1. A device, comprising:
one or more memories; and
one or more processors to:
receive a file that is to be analyzed for malware;
open the received file in a secure environment;
install a secondary file in the secure environment to permit a malicious object of the received file to embed a malicious payload of the received file in the secondary file,
the secondary file being a file within a directory of a computing environment that runs an application or program that opens the received file;
determine that the secondary file in the secure environment has been accessed based on the received file being opened by a user;
analyze the secondary file in the secure environment to identify malware; and
perform an action associated with the received file based on the secondary file being analyzed,
where the secure environment is implemented on a computing resource of a cloud environment, and
where the one or more processors, when performing the action associated with the received file, are to:
quarantine a source of the received file based on identifying the malware.
2. The device of claim 1 , where the one or more processors, when determining that the secondary file has been accessed, are to:
monitor a directory of the secure environment after opening the received file; and
detect that the secondary file has been modified based on monitoring the directory.
3. The device of claim 1 , where the one or more processors, when determining that the secondary file has been accessed, are to:
monitor a designated set of files, in the secure environment, associated with the received file,
the designated set of files comprising the secondary file.
4. The device of claim 1 , where the one or more processors, when analyzing the secondary file in the secure environment, are to:
conduct at least one of a static analysis of the secondary file, a signature-based analysis of the secondary file, or a statistical-based analysis of the secondary file to detect the malware.
5. The device of claim 1 , where the one or more processors, when analyzing the secondary file in the secure environment, are to:
conduct at least one of a dynamic analysis of the secondary file or a behavior-based analysis of the secondary file to detect the malware.
6. The device of claim 1 , where the one or more processors, when analyzing the secondary file in the secure environment, are to:
identify an application associated with the secondary file, and
use the application to open the secondary file in the secure environment.
7. The device of claim 1 , where the one or more processors are further to:
prevent the received file from reaching an intended target of the received file based on identifying the malware.
8. The device of claim 1 , where the one or more processors are further to:
update a malware database to include information associated with the malware based on identifying the malware.
9. The device of claim 1 , where the one or more processors are further to:
place information associated with the source of the received file on a blacklist based on identifying the malware.
10. The device of claim 1 , where the one or more processors are further to:
remove, based on identifying the malware, the malicious object from the received file to generate a clean file; and
transmit the clean file to an intended target of the received file.
11. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
receive a file that is to be analyzed for malware;
open the received file in a first secure environment;
install a secondary file in the first secure environment to permit a malicious object of the received file to embed a malicious payload of the received file in the secondary file,
the secondary file being a file within a directory of a computing environment that runs an application or program that opens the received file;
determine that the secondary file in the first secure environment has been accessed after opening, by a user, the received file;
open the secondary file in a second secure environment to identify malware; and
perform an action associated with the received file based on identifying the malware,
where the first secure environment is implemented on a computing resource of a cloud environment, and
where the one or more instructions, that cause the one or more processors to perform the action associated with the received file, cause the one or more processors to:
quarantine a source of the received file based on identifying the malware.
12. The non-transitory computer-readable medium of claim 11 , where the one or more instructions, that cause the one or more processors to open the secondary file in the second secure environment, cause the one or more processors to:
copy the secondary file, and
open the copy of the secondary file in the second secure environment,
where the second secure environment is separate from the first secure environment.
13. The non-transitory computer-readable medium of claim 11 , where the one or more instructions further cause the one or more processors to:
prevent the received file from reaching an intended target of the received file based on identifying malware.
14. The non-transitory computer-readable medium of claim 11 , where the one or more instructions further cause the one or more processors to:
update a malware database to include information associated with the malware.
15. The non-transitory computer-readable medium of claim 11 , where the one or more instructions, further cause the one or more processors to
place the source of the received file on a blacklist based on identifying the malware.
16. The non-transitory computer-readable medium of claim 11 , where the one or more instructions further cause the one or more processors to:
provide information regarding the malware to a security platform to modify a future operation of the security platform.
17. A method, comprising:
receiving, by one or more devices of a security platform, a file that into be analyzed for malware;
opening, by at least one of the one or more devices, the received file in a secure environment;
installing, by at least one of the one or more devices, a secondary file in the secure environment to permit a malicious object of the received file to embed a malicious payload of the received file in the secondary file,
the secondary file being a file within a directory of a computing environment that runs an application or program that opens the received file;
determining, by at least one of the one or more devices, that the secondary file in the secure environment has been modified based on the received file being opened by a user;
opening, by at least one of the one or more devices, the secondary file in the secure environment;
identifying, by at least one of the one or more devices, malware after opening the secondary file; and
performing, by at least one of the one or more devices, an action associated with the received file based on identifying the malware,
where the secure environment is implemented on a computing resource of a cloud environment, and
where performing the action comprises:
quarantining a source of the received file based on identifying the malware.
18. The method of claim 17 , further comprising:
removing the malicious object from the received file based on identifying the malware to generate a clean file; and
transmitting the clean file to an intended target of the received file.
19. The method of claim 17 further comprising:
providing information regarding the malware to the security platform to modify a future operation of the security platform.
20. The method of claim 17 , where performing the action comprises:
placing the source of the received file on a blacklist based on identifying the malware.