Systems and methods for detecting malware in obfuscated scripts

1. A method for detecting malware in an obfuscated script, the method comprising:

receiving the obfuscated script on a computing device written in a first coding language, wherein a malware scanner on the computing device is incompatible with the first coding language;

identifying the first coding language based on detected keywords and operators in the obfuscated script;

converting each line of the obfuscated script in the first coding language into a respective modified abstract syntax tree (mAST);

receiving artifacts of the obfuscated script by executing at least one mAST using a universal emulator;

scanning the artifacts for malware using the malware scanner; and

in response to detecting the malware in the obfuscated script based on the scanning the artifacts, performing a remediation action on the obfuscated script.

2. The method of claim 1 , wherein the converting further comprises performing tokenization, multi-line rewrites, and token rewrites.

3. The method of claim 1 , wherein the converting further comprises mapping flows in the obfuscated script.

4. The method of claim 1 , wherein the remediation action comprises one of quarantining the obfuscated script and/or the artifacts, removing the obfuscated script and/or the artifacts from the computing device, and performing a recovery process on the computing device.

5. The method of claim 1 , wherein the artifacts comprise another script written in a second coding language incompatible with the malware scanner, further comprising:

identifying the second coding language based on detected keywords and operators in the another script;

converting each line of the another script in the second coding language into another respective mAST;

receiving additional artifacts of the another script by executing at least one of the another respective mAST using the universal emulator;

scanning the additional artifacts for malware using the malware scanner; and

in response to detecting the malware in the another script based on the scanning the additional artifacts, performing the remediation action on the another script.

6. The method of claim 1 , wherein the universal emulator is configured to execute an operation of the at least one mAST to generate a given artifact, and wherein the malware scanner is configured to scan the given artifact.

7. A system for detecting malware in an obfuscated script, comprising:

at least one memory;

at least one hardware processor coupled with the at least one memory and configured, individually or in combination, to:

receive the obfuscated script on a computing device written in a first coding language, wherein a malware scanner on the computing device is incompatible with the first coding language;

identify the first coding language based on detected keywords and operators in the obfuscated script;

convert each line of the obfuscated script in the first coding language into a respective modified abstract syntax tree (mAST);

receive artifacts of the obfuscated script by executing at least one mAST using a universal emulator;

scan the artifacts for malware using the malware scanner; and

in response to detecting the malware in the obfuscated script based on the scanning the artifacts, perform a remediation action on the obfuscated script.

8. The system of claim 7 , wherein the at least one hardware processor is configured to convert by performing tokenization, multi-line rewrites, and token rewrites.

9. The system of claim 7 , wherein the at least one hardware processor is configured to convert by mapping flows in the obfuscated script.

10. The system of claim 7 , wherein the remediation action comprises one of quarantining the obfuscated script and/or the artifacts, removing the obfuscated script and/or the artifacts from the computing device, and performing a recovery process on the computing device.

11. The system of claim 7 , wherein the artifacts comprise another script written in a second coding language incompatible with the malware scanner, wherein the at least one hardware processor is configured to:

identify the second coding language based on detected keywords and operators in the another script;

convert each line of the another script in the second coding language into another respective mAST;

receive additional artifacts of the another script by executing at least one of the another respective mAST using the universal emulator;

scan the additional artifacts for malware using the malware scanner; and

in response to detecting the malware in the another script based on the scanning the additional artifacts, perform the remediation action on the another script.

12. The system of claim 7 , wherein the universal emulator is configured to execute an operation of the at least one mAST to generate a given artifact, and wherein the malware scanner is configured to scan the given artifact.

13. A non-transitory computer readable medium storing thereon computer executable instructions for detecting malware in an obfuscated script, including instructions for:

receiving the obfuscated script on a computing device written in a first coding language, wherein a malware scanner on the computing device is incompatible with the first coding language;

identifying the first coding language based on detected keywords and operators in the obfuscated script;

converting each line of the obfuscated script in the first coding language into a respective modified abstract syntax tree (mAST);

receiving artifacts of the obfuscated script by executing at least one mAST using a universal emulator;

scanning the artifacts for malware using the malware scanner; and

in response to detecting the malware in the obfuscated script based on the scanning the artifacts, performing a remediation action on the obfuscated script.

14. The non-transitory computer readable medium of claim 13 , wherein the instruction for converting further comprises instructions for performing tokenization, multi-line rewrites, and token rewrites.

15. The non-transitory computer readable medium of claim 13 , wherein the instruction for converting further comprises instructions for mapping flows in the obfuscated script.

16. The non-transitory computer readable medium of claim 13 , wherein the remediation action comprises one of quarantining the obfuscated script and/or the artifacts, removing the obfuscated script and/or the artifacts from the computing device, and performing a recovery process on the computing device.

17. The non-transitory computer readable medium of claim 13 , wherein the artifacts comprise another script written in a second coding language incompatible with the malware scanner, further comprising instructions for:

identifying the second coding language based on detected keywords and operators in the another script;

converting each line of the another script in the second coding language into another respective mAST;

receiving additional artifacts of the another script by executing at least one of the another respective mAST using the universal emulator;

scanning the additional artifacts for malware using the malware scanner; and

in response to detecting the malware in the another script based on the scanning the additional artifacts, performing the remediation action on the another script.

18. The non-transitory computer readable medium of claim 13 , wherein the universal emulator is configured to execute an operation of the at least one mAST to generate a given artifact, and wherein the malware scanner is configured to scan the given artifact.